Could not find a part of the path bin roslyn csc exe

Question

I am trying to run  Asp net MVC project retrieved from TFS source control  I have added all assembly references and I am able to build and compile successfully without any error or warning   But I get the following error in the browser      Could not find a part of the path    C  B8akWorkspace B8akProject B8akSolution B8AK Portal bin roslyn csc exe     Here is a full screenshot of the error page     After few days of research  I understood that Roslyn is  Net compiler platform that offers advance compiling features  However  I do not understand why my build is trying to find  bin roslyn csc exe because I did not configure anything related to Roslyn nor I intend to use Roslyn in my project

User · Answer

Upgrading Microsoft CodeDom Providers DotNetCompilerPlatform from 1 0 0 to 1 0 1 fixed this for me

User · Answer

Issue  Be aware that the NuGet PM breaks the Rosalyn behavior   Click Tools  gt  NuGet Package Manager  gt  Manage NuGet Packages for Solution  If an update Exists for Microsoft CodeDom Providers DotNetCompilerPlatform  Microsoft Net Compilers  or Microsoft Net Compilers netcore  update them and the Solution will break   This occurs because the ASP Sites templates are set to use specific versions at project creation   To See the problem  click Show All Files in the Solution Explorer   Fix  At project creation the   WebProjectOutputDir  bin doesn t exist  therefore when Rosalyn is added as a dependency by NuGet it installs it properly  After Updating the Solution Packages  the   WebProjectOutputDir  bin directory looks like so     WebProjectOutputDir  bin bin rosalyn  The easiest fix is to Cut  amp  Paste rosalyn to the proper location  and then delete the extra bin folder   You can now Refresh the page and the site will load

User · Answer

For VS 2019 remove the following node completely    lt system codedom gt   lt  system codedom gt

User · Answer

Your build is trying to find  bin roslyn csc exe because the following packages have been added to your project  Just review your packages config file  you can have both of them there  Microsoft CodeDom Providers DotNetCompilerPlatform Microsoft Net Compilers      What is Roslyn and Who added them packages  in the project   If you   re using  net Framework 4 5 2 to create projects   using VS2015  you might have noticed that the project templates use   Roslyn by default  Actually Roslyn is one of open-source   compilers for  NET languages from Microsoft       Why should we delete Roslyn     If your project has Roslyn references and you are interested to deploy   it no server  you will get unwanted errors on the website as many   hosting providers still have not upgraded their servers and hence do   not support Roslyn  To resolve this issue  you will need to remove the   Roslyn compiler from the project template    if you are not interested in using Roslyn  follow steps bellow to delete it  1   Remove NuGet packages  use the following commands from Nuget Package Console   PM gt  Uninstall-package Microsoft CodeDom Providers DotNetCompilerPlatform PM gt  Uninstall-package Microsoft Net Compilers   2   After you do this  your web config file should be auto-updated  In case it is not  look for the below code in web config file and if it is found  delete this piece of code    lt system codedom gt       lt compilers gt         lt compiler language  c  cs csharp  extension   cs  type  Microsoft CodeDom Providers DotNetCompilerPlatform CSharpCodeProvider  Microsoft CodeDom Providers DotNetCompilerPlatform  Version 1 0 0 0  Culture neutral  PublicKeyToken 31bf3856ad364e35  warningLevel  4  compilerOptions   langversion 6  nowarn 1659 1699 1701  gt  lt  compiler gt         lt compiler language  vb vbs visualbasic vbscript  extension   vb  type  Microsoft CodeDom Providers DotNetCompilerPlatform VBCodeProvider  Microsoft CodeDom Providers DotNetCompilerPlatform  Version 1 0 0 0  Culture neutral  PublicKeyToken 31bf3856ad364e35  warningLevel  4  compilerOptions   langversion 14  nowarn 41008  define  MYTYPE   amp quot Web  amp quot   optionInfer   gt  lt  compiler gt       lt  compilers gt   lt  system codedom gt

User · Answer

Per a comment by Daniel Neel above     version 1 0 3 of the Microsoft CodeDom Providers DotNetCompilerPlatform Nuget package works for me  but version 1 0 6 causes the error in this question  Downgrading to 1 0 3 resolved this issue for me

User · Answer

I had this error after renaming a solution and some included projects  and playing around with removing nuget packages  I compared the new project with the last working project  and found the following lines were missing and needed to be added back in      lt Import Project     packages Microsoft CodeDom Providers DotNetCompilerPlatform 1 0 0 build Microsoft CodeDom Providers DotNetCompilerPlatform props  Condition  Exists     packages Microsoft CodeDom Providers DotNetCompilerPlatform 1 0 0 build Microsoft CodeDom Providers DotNetCompilerPlatform props      gt     lt Import Project     packages Microsoft Net Compilers 1 0 0 build Microsoft Net Compilers props  Condition  Exists     packages Microsoft Net Compilers 1 0 0 build Microsoft Net Compilers props      gt     lt Import Project    MSBuildExtensionsPath    MSBuildToolsVersion  Microsoft Common props  Condition  Exists    MSBuildExtensionsPath    MSBuildToolsVersion  Microsoft Common props      gt    Doing so resolved the issue for me

User · Answer

As already noted by https   stackoverflow com questions 32780315 34391473   the quick fix is to use the package manager   Tools   Nuget Package Manager   Package Manager Console  to run   Update-Package Microsoft CodeDom Providers DotNetCompilerPlatform -r      But an alternative solution  which automatically and silently recreates your packages if they are missing  is to remove an attribute of your project s Web config file   Web config is in the same directory as your  csproj file    Open the Web config file in a text editor  or inside Visual Studio    - In the tag configuration   system codedom   compilers   compiler language  c  cs csharp   completely remove the type attribute    lt  xml version  1 0  encoding  utf-8   gt   lt configuration gt     lt  --     -- gt     lt system codedom gt       lt compilers gt         lt compiler language  c  cs csharp  extension   cs          type  Microsoft CodeDom Providers DotNetCompilerPlatform CSharpCodeProvider  Microsoft CodeDom Providers DotNetCompilerPlatform  Version 1 0 5 0  Culture neutral  PublicKeyToken 31bf3856ad364e35          warningLevel  4  compilerOptions   langversion default  nowarn 1659 1699 1701   gt         lt compiler language  vb vbs visualbasic vbscript  extension   vb          type  Microsoft CodeDom Providers DotNetCompilerPlatform VBCodeProvider  Microsoft CodeDom Providers DotNetCompilerPlatform  Version 1 0 5 0  Culture neutral  PublicKeyToken 31bf3856ad364e35          warningLevel  4  compilerOptions   langversion default  nowarn 41008  define  MYTYPE   amp quot Web  amp quot   optionInfer    gt       lt  compilers gt     lt  system codedom gt   lt  configuration gt    In short  remove the line that starts with type  Microsoft CodeDom Providers DotNetCompilerPlatform CSharpCodeProvider  Microsoft    Presumably  the same fix works for Visual Basic as well as for Csharp  but I have not tried it    Visual Studio will take care of the rest  No more Server Error in     Application   In the example code I provided in the zip file above you will now get HTTP Error 403  when you hit Ctrl F5     Try replacing http   localhost 64195 in your web browser with http   localhost 64195 api products  The web API now displays as it should     As a provocation  I tried removing the whole package directory of my Visual Studio solution  It was automatically and silently recreated as soon as I  re- built it     Last but not least  here is code that reproduces the error   http   schulze 000webhostapp com vs SrvrErr-reproduce zip  Originally from   https   github com aspnet AspNetDocs tree master aspnet web-api overview advanced calling-a-web-api-from-a-net-client sample server ProductsApp

User · Answer

In my case I just needed to go to the bin directory in Visual Studio Solution Explorer  web application project  and include the roslyn project directly  By right clicking the folder and selecting Include In Project   And check in the solution again to trigger the build process   The roslyn folder was not included by default

User · Answer

I ran into this issue with the publishing pipeline  which produces a  PublishedWebsites directory   and used this as a Target in the project    lt Target Name  CopyRoslynCompilerFilesToPublishedWebsitesDirectory  AfterTargets  AfterBuild  Condition  Exists    OutDir   PublishedWebsites   TargetName     gt       lt Copy SourceFiles    RoslyCompilerFiles   DestinationFolder    OutDir   PublishedWebsites   TargetName  bin roslyn  ContinueOnError  true  SkipUnchangedFiles  true    gt   lt  Target gt    The downside is that there will be two copies of the Roslyn files in the output

User · Answer

FYI     As of 8 31 2017 upgrading to Microsoft CodeDom Providers DotNetCompilerPlatform 1 0 7 is works

User · Answer

I ran into this problem after updating some packages through NuGet  A rebuild  instead of a normal build  has worked for me

User · Answer

None of the other answers worked for me   After doing a folder compare before after vs my expected committed files  i discovered that GIT was ignoring a required folder   If you are tracking the compiler in a repository  make sure the BUILD folder is tracked   If it s not  the compiler won t ever be built and will throw this exact error after publish   I added this line to my  gitignore file       packages Microsoft CodeDom Providers DotNetCompilerPlatform 2 0 1 build    and now it s deploying to other computers properly

User · Answer

In my situation  our team don t want to keep  packages  folder  so we put all dlls in other directory like  sharedlib    I used build event to solve this problem   if    ConfigurationName       Release    goto  release   else   goto exit     release if not exist   TargetDir  roslyn mkdir   TargetDir  roslyn  copy  Y    ProjectDir       Shared Lib Microsoft CodeDom Providers DotNetCompilerPlatform 2 0 1 tools Roslyn45       TargetDir  roslyn  goto  exit   exit

User · Answer

I had the same problem when installing my application on the server when everything worked perfectly on localhost   None of these solutions woorked  I always had the same error   Could not find a part of the path  C  inetpub wwwroot myApp bin roslyn csc exe    I ended up doing this     on my setup project  right clic  view   file system create a bin roslyn folder select add   files and add all files from packages Microsoft Net Compilers 1 3 2 tools   This solved my problem

User · Answer

To prevent the build from also copying the Roslyn files to the bin directory  you have to also comment out this line that gets placed at the top of your Web application project    lt  --   lt Import Project           DAS packages Microsoft CodeDom Providers DotNetCompilerPlatform 1 0 1 build Microsoft CodeDom Providers DotNetCompilerPlatform props  Condition  Exists           DAS packages Microsoft CodeDom Providers DotNetCompilerPlatform 1 0 1 build Microsoft CodeDom Providers DotNetCompilerPlatform props      gt  -- gt

User · Answer

I experienced this error on a Jenkins build server running MSBuild  which outputs the build files to a separate folder location   PublishedWebsites   Exactly the same - the roslyn folder was not in the bin directory  and all the roslyn files were lumped in with the bin files    igor-semin  s answer was the only thing that worked for me  as I am using the C  6 language features  I cannot simply uninstall the nuget packages as per other answers   but as I am also running CodeAnalysis  I was getting another error on my deployment target server    An attempt to override an existing mapping was detected for type Microsoft CodeAnalysis ICompilationUnitSyntax with name     currently mapped to type Microsoft CodeAnalysis CSharp Syntax CompilationUnitSyntax  to type Microsoft CodeAnalysis VisualBasic Syntax CompilationUnitSyntax    The reason for this is that as the roslyn files are getting dumped into the main bin directory  when you run the xcopy to recreate them in the nested roslyn folder  you now have 2 copies of these files being compiled and there is a clash between them  After much frustration I decided on a  hack  fix - an additional post-build task to delete these files from the bin directory  removing the conflict    The  csproj of my offending projects now looks like                       more here                           lt PropertyGroup gt      lt PostBuildEvent gt     if not exist    WebProjectOutputDir  bin Roslyn  md    WebProjectOutputDir  bin Roslyn     start  MIN xcopy  s  y  R    OutDir roslyn         WebProjectOutputDir  bin Roslyn    lt  PostBuildEvent gt   lt  PropertyGroup gt   lt Target Name  DeleteDuplicateAnalysisFiles  AfterTargets  AfterBuild  gt      lt  -- Jenkins now has copies of the following files in both the bin directory and the  bin rosyln  directory  Delete from bin  -- gt      lt ItemGroup gt        lt FilesToDelete Include    WebProjectOutputDir  bin Microsoft CodeAnalysis  dll    gt      lt  ItemGroup gt      lt Delete Files    FilesToDelete     gt   lt  Target gt                        more here

User · Answer

The following solved this issue for me    Updating to the latest version of Visual Studio 2017  using the installer app  Clean and rebuild the solution

User · Answer

my solution is using Nuget to update below items to latest version   - Microsoft Net Compilers  - Microsoft CodeDom Providers DotNetCompilerPlatform Then rebuilt the project  Since my project is a website so no   csproj file  The error above appears when I tried to view a cshtml in browser   The error fixed after the two items above updated to latest version  I am in VS2015 and windows7 SP1

User · Answer

In my case I had this issue when i was running two visual studio IDE simultaneously  So the solution was to clean the project and close the other instance

User · Answer

In my case  before trying any of the other solutions  I switched to a  quot Release quot  configuration  rebuilt  the folder got created  and then switched back to  quot Debug quot   while the folder remained intact  This was a checkout from source control of an older solution and apparently the original  automatic  package restore and building the project didn t create that folder in the bin directory  Note that at time of writing this  the blamed component has reached v 2

User · Answer

TL  DR  run this in the Package Manager Console   Update-Package Microsoft CodeDom Providers DotNetCompilerPlatform -r  More information  This problem is not related to Visual Studio itself  so answers suggesting adding build steps to copy files over are rather a workaround  Same with adding compiler binaries manually to the project   The Roslyn compiler comes from a NuGet package and there is was a bug in some versions of that package  I don t know exactly which ones   The solution is to reinstall upgrade that package to a bug-free version  Originally before I wrote the answer back in 2015 I fixed it by installing following packages at specific versions    Microsoft Net Compilers 1 1 1 Microsoft CodeDom Providers DotNetCompilerPlatform 1 0 1   Then I looked into  csproj and made sure that the paths to packages are correct  in my case       packages      inside tags  lt ImportProject gt  on top and in  lt Target gt  with name  EnsureNuGetPackageBuildImports  on the bottom  This is on MVC 5 and  NET Framework 4 5 2

User · Answer

In my case by just Deleting everything inside the bin folder and recompiling did all the work for me

User · Answer

Open the project file and remove all references with Import Project     packages Microsoft CodeDom Providers DotNetCompilerPlatform 1 0 0      Open web config and remove all system codedom compilers attributes

User · Answer

Here is a more MSBuild way of doing this      lt Target Name  CopyRoslynFiles  AfterTargets  AfterBuild  Condition     Disable CopyWebApplication  And    OutDir         OutputPath    gt       lt ItemGroup gt         lt RoslynFiles Include    CscToolPath       gt       lt  ItemGroup gt       lt MakeDir Directories    WebProjectOutputDir  bin roslyn    gt       lt Copy SourceFiles    RoslynFiles   DestinationFolder    WebProjectOutputDir  bin roslyn  SkipUnchangedFiles  true  Retries    CopyRetryCount   RetryDelayMilliseconds    CopyRetryDelayMilliseconds     gt   lt  Target gt    But I notice that the roslyn files are also in my bin directory  not in a folder    The app seems to work  though

User · Answer

I was also having same issue while running the project  Here are the steps that I followed    Right click in solution select Clean solution  After clean succeeded Again build your project Run the project again   This time I didn t see the same error  This works as expected

User · Answer

A clean and rebuild worked for me

User · Answer

I had to change the WebAPI and MVC project files to not build views     lt MvcBuildViews gt false lt  MvcBuildViews gt    This resolved my TFS 2015 Build server error with roslyn  Still not sure why csc exe was copied to  bin csc exe  yet the publish process was looking for  bin Roslyn csc exe   couldn t find the transformation causing that discrepancy

User · Answer

Right click on your project and select Manage Nuget Packages Find  Microsoft CodeDom Providers DotNetCompilerPlatform  Simply Update to an older or newer version  doesn t matter which   and then update again back to your original version    This re-installs all the dependencies and files of the package  like csc exe

User · Answer

You need to install Microsoft CodeDom Providers DotNetCompilerPlatform BinFix  was especially created for that error

User · Answer

Reboot Windows   This is the only solution that worked for me after trying rebuild  delete contents of bin and rebuild  restart Visual Studio   It s yet another example of how terrible C   NET build tools are   I think  after reading many of the answers   the overall conclusion is that the cause and solution of this problem heavily depends on the setup and project  so if one answer does not work  just try another  Try non-intrusive destructive solutions  such as restarting Visual Studio  rebooting  rebuilding  etc   FIRST  before messing with NuGet packages or reinstalling development tools  Good luck    NOTE  Using Visual Studio 2019  and project file was originally created in Visual Studio 2015  Maybe this helps someone investigate the issue    EDIT  Could this be caused by not rebooting after installing modifying the Visual Studio installation or updating Visual Studio when the installer prompts to reboot

User · Answer

This can be done in the following easy way-    Create a new project of similar type anywhere in your system  Build it and copy over the roslyn folder to your bin directory

User · Answer

In my case I have had issue in Jenkins when it tried to deploying it in Octopus with following error   MSBUILD   OctoPack error OCT-1676060969  Failed to build the path for   bin roslyn csc exe  relative to  T  workspace machine engine Machine engine Test   Invalid URI  The format of the URI could not be determined   See the inner exception for more details   T  workspace machine engine Machine engine Test Machine engine Test csproj  MSBUILD   OctoPack error OCT-1676060969  System Exception  Failed to build the path for   bin roslyn csc exe  relative to  T  workspace machine engine Machine engine Test   Invalid URI  The format of the URI could not be determined   See the inner exception for more details  --- gt  System UriFormatException  Invalid URI  The format of the URI could not be determined   T  workspace machine engine Machine engine Test Machine engine Test csproj  MSBUILD   OctoPack error OCT-1676060969     at System Uri CreateThis String uri  Boolean dontEscape  UriKind uriKind   T  workspace machine engine Machine engine Test Machine engine Test csproj  MSBUILD   OctoPack error OCT-1676060969     at System Uri  ctor String uriString   T  workspace machine engine Machine engine Test Machine engine Test csproj  MSBUILD   OctoPack error OCT-1676060969     at OctoPack Tasks Util OctopusPhysicalFileSystem GetPathRelativeTo String fullPath  String relativeTo  in Z  buildAgent workDir 20ba9f2e0d5e4022 source OctoPack Tasks Util OctopusPhysicalFileSystem cs line 211  T  workspace machine engine Machine engine Test Machine engine Test csproj  MSBUILD   OctoPack error OCT-1676060969     --- End of inner exception stack trace ---  T  workspace machine engine Machine engine Test Machine engine Test csproj  MSBUILD   OctoPack error OCT-1676060969     at OctoPack Tasks Util OctopusPhysicalFileSystem GetPathRelativeTo String fullPath  String relativeTo  in Z  buildAgent workDir 20ba9f2e0d5e4022 source OctoPack Tasks Util OctopusPhysicalFileSystem cs line 224  T  workspace machine engine Machine engine Test Machine engine Test csproj  MSBUILD   OctoPack error OCT-1676060969     at OctoPack Tasks CreateOctoPackPackage AddFiles XContainer nuSpec  IEnumerable 1 sourceFiles  String sourceBaseDirectory  String targetDirectory  String relativeTo  in Z  buildAgent workDir 20ba9f2e0d5e4022 source OctoPack Tasks CreateOctoPackPackage cs line 443  T  workspace machine engine Machine engine Test Machine engine Test csproj  MSBUILD   OctoPack error OCT-1676060969     at OctoPack Tasks CreateOctoPackPackage Execute   in Z  buildAgent workDir 20ba9f2e0d5e4022 source OctoPack Tasks CreateOctoPackPackage cs line 190  T  workspace machine engine Machine engine Test Machine engine Test csproj  Done Building Project  T  workspace machine engine Machine engine Test Machine engine Test csproj   default targets  -- FAILED   Cause  After spending some time  I was using an internal developed component that was using Microsoft Net Compilers  The reason the internal component was using Microsoft Net Compilers was to overcome this issue  C   throw invalid expression compilation  and was solved this way  How to use C  7 with Visual Studio 2015    This result in  when I installed the component on the main program  the Microsoft Net Compilers get added it selves automatically   Solution  My work around was  uninstall following from our internal component by  following  malikKhalil answer   PM gt  Uninstall-package Microsoft CodeDom Providers DotNetCompilerPlatform PM gt  Uninstall-package Microsoft Net Compilers   And chose C  7 compiler in Jenkins instead of C  6 and rebuild  this is to ensure everything is working and building correctly   Than finally in my main program I tried to update my internal component  And everything than build again  It has built without any problems or issues

User · Answer

The answer for this is different for Website project and Web application Project  The underlying issue is same that  NuGet package is behaving differently on different machine  It may be rights issue or some execution policy which stops it from copying to Bin folder As you know Roslyn is new compiler   you should have it in Bin folder for these Projects Go to your website NuGet Packages  check this Folder  Microsoft CodeDom Providers DotNetCompilerPlatform 2 0 0  code packages Microsoft CodeDom Providers DotNetCompilerPlatform 2 0 0 Do you see it    Can you see code packages Microsoft CodeDom Providers DotNetCompilerPlatform 2 0 0 tools RoslynLatest in it  Now as part of compiling this Folder should get copied to your website under bin like this   code WebSite1 Bin Roslyn  some how that is not happening for you   Try running Visual studio as Admin   Copy Roslyn folder manually  Try uninstall and install of NuGet Package  Remember this package compile your folder and if its not there you cannot compile anything and so you cannot add anything too  Try copying this package to offline version tools -  options-  nuget package Manager- Package source-  Microsoft Visual Studio Offline Packages  C  Program Files  x86  Microsoft SDKs NuGetPackages

User · Answer

As noted in an issue in the Roslyn project on GitHub  a solution  that worked for me  is to simply unload and reload the project in Visual Studio   The  bin roslyn  folder wasn t created on build or rebuild until I reloaded the project

User · Answer

Updating nuget packages worked for me  Right click on the solution   Manage NuGet packages for solution  and update all the packages and specially  Microsoft Net Compilers  and Microsoft CodeDom Providers DotNetCompilerPlatform

User · Answer

The problem with the default VS2015 templates is that the compiler isn t actually copied to the tfr bin roslyn  directory  but rather the  outdir  roslyn  directory  Add this code in your  csproj file    lt Target Name  CopyRoslynFiles  AfterTargets  AfterBuild  Condition     Disable CopyWebApplication  And    OutDir         OutputPath    gt       lt ItemGroup gt         lt RoslynFiles Include    CscToolPath       gt       lt  ItemGroup gt       lt MakeDir Directories    WebProjectOutputDir  bin roslyn    gt       lt Copy SourceFiles    RoslynFiles   DestinationFolder    WebProjectOutputDir  bin roslyn  SkipUnchangedFiles  true  Retries    CopyRetryCount   RetryDelayMilliseconds    CopyRetryDelayMilliseconds     gt   lt  Target gt

User · Answer

I had this issue on the server I was deploying to  and determined that I did not need      Microsoft CodeDom Providers DotNetCompilerPlatform   So  I uninstalled it via nuget  and removed the reference in the web config  No more issues   I originally tried to added target node to the  proj file as mentioned in some of the other answers  but that just lead to another error where the msbuild could not copy the pagefile sys which seemed from what I read to be a bug in the nuget package

User · Answer

If you were adding ASPNETCOMPILER to compile your Razor views in MVC  like in this StackOverflow question  then change PhysicalPath to place where Roslyn nuget package is located  usually pointed via  CscToolPath variable     lt Target Name  AfterBuild  Condition     MvcBuildViews     true   gt   lt AspNetCompiler VirtualPath  temp  PhysicalPath    CscToolPath     gt

User · Answer

I followed these steps and it worked perfectly   Delete all the bin and obj folders  Clean solution and rebuild Run this command in powershell   Update-Package Microsoft CodeDom Providers DotNetCompilerPlatform -r

User · Answer

Too late for an answer but still posting incase it helps anyone  Following the below steps fixed the error for me    delete packages folder open VS rebuild observe that NuGet packages are restored  but bin roslyn isnt created unload project reload project rebuild observe that the bin roslyn has been created now

User · Answer

Clean Solution Rebuild Solution   These two steps worked for me

User · Answer

Delete the Bin folder in your solution explorer and Build the solution again  That would solve the problem

User · Answer

This is a known issue with Microsoft CodeDom Providers DotNetCompilerPlatform 1 0 6  Downgrading to 1 0 5 fixed this for me

User · Answer

So  Rob Cannon s answer essentially worked for me  but I had to tweak a handful of the options  Specifically  I had to remove the condition on the target  as well as change the Include attribute  as  CscToolPath was empty when the project was being built on our build server  Curiously   CscToolPath was NOT empty when running locally    lt Target Name  CopyRoslynFiles  AfterTargets  AfterBuild   gt     lt ItemGroup gt       lt RoslynFiles Include    SolutionDir packages Microsoft Net Compilers 1 1 1 tools      gt     lt  ItemGroup gt     lt MakeDir Directories    WebProjectOutputDir  bin roslyn    gt     lt Copy SourceFiles    RoslynFiles   DestinationFolder    WebProjectOutputDir  bin roslyn  SkipUnchangedFiles  true  Retries    CopyRetryCount   RetryDelayMilliseconds    CopyRetryDelayMilliseconds     gt   lt  Target gt

User · Answer

Other than deleting the Bin diretory from all projects inside the solution  delete the obj folders too   In the main solution diretory remove the folder  vs  Worked for me when trying to bring an already done project into a blank solution created on git

User · Answer

In my case  similar to Basim  there was a NuGet package that was telling the compiler we needed C  6  which we didn t   We had to remove the NuGet package Microsoft CodeDom Providers DotNetCompilerPlatform which then removed     lt package id  Microsoft CodeDom Providers DotNetCompilerPlatform  version  1 0 0  targetFramework  net452    gt  from the packages config file  lt system codedom gt     lt compilers gt        lt compiler language  c  cs csharp  extension   cs  type  Microsoft CodeDom Providers DotNetCompilerPlatform CSharpCodeProvider  Microsoft CodeDom Providers DotNetCompilerPlatform  Version 1 0 0 0  Culture neutral  PublicKeyToken 31bf3856ad364e35  warningLevel  4  compilerOptions   langversion 6  nowarn 1659 1699 1701    gt        lt compiler language  vb vbs visualbasic vbscript  extension   vb  type  Microsoft CodeDom Providers DotNetCompilerPlatform VBCodeProvider  Microsoft CodeDom Providers DotNetCompilerPlatform  Version 1 0 0 0  Culture neutral  PublicKeyToken 31bf3856ad364e35  warningLevel  4  compilerOptions   langversion 14  nowarn 41008  define  MYTYPE   amp quot Web  amp quot   optionInfer     gt    lt  compilers gt   lt  system codedom gt    In the system codedom node  you can see why it was bringing in roslyn  compilerOptions   langversion 6

User · Answer

I had this error for Microsoft CodeDom Providers DotNetCompilerPlatform 1 06 but also with 1 0 7 that worked for  PrisonerZERO  However when Microsoft released 1 0 8 2017-10-18 it finally started working for me again and I did not have to downgrade   https   www nuget org packages Microsoft CodeDom Providers DotNetCompilerPlatform

User · Answer

I had the same problem after updating DotNetCompilerPlatform  Solved by Restarting Visual Studio   Clean Project   Build Project

User · Answer

The problem with the default VS2015 templates is that the compiler isn t actually copied to the  outdir  PublishedWebsites tfr bin roslyn  directory  but rather the  outdir  roslyn  directory  This is likely different from your local environment since AppHarbor builds apps using an output directory instead of building the solution  in-place    To fix it  add the following towards end of  csproj file right after xml block  lt Target Name  EnsureNuGetPackageBuildImports  BeforeTargets  PrepareForBuild  gt     lt  Target gt    lt PropertyGroup gt     lt PostBuildEvent gt      if not exist    WebProjectOutputDir  bin Roslyn  md    WebProjectOutputDir  bin Roslyn      start  MIN xcopy  s  y  R    OutDir roslyn         WebProjectOutputDir  bin Roslyn     lt  PostBuildEvent gt   lt  PropertyGroup gt    Reference  https   support appharbor com discussions problems 78633-cant-build-aspnet-mvc-project-generated-from-vstudio-2015-enterprise

User · Answer

I have webproject without csproj file and solutions mentiond here did not work for me   Changing target  NET framework  reinstalling packages  Update-Package -reinstall  and then building the project worked for me  You can even change target framework back after this operation make suere you reinstall nuget packages again after

User · Answer

After trying all of the fixes with no cigar I fixed it by updating this Nuget Package in Visual Studios   Microsoft CodeDom Providers DotNetCompilerPlatform  Mine was from 1 0 0 to 2 0 0 for reference  The error no longer shows

User · Answer

A lot of these answers are referring to the Nuget packages and or cleaning and reloading your project   If you have WCF service references and invalid endpoints  you can also get this error message  Make sure your endpoints are correct and update the service configuration with the correct endpoint in the  config and when you configure the service reference from the GUI

User · Answer

Add PropertyGroup to your  csproj file    lt PropertyGroup gt     lt PostBuildEvent gt      if not exist    WebProjectOutputDir  bin Roslyn  md    WebProjectOutputDir  bin Roslyn            start  MIN xcopy  s  y  R    OutDir roslyn         WebProjectOutputDir  bin Roslyn     lt  PostBuildEvent gt   lt  PropertyGroup gt

[c#] Could not find a part of the path ... bin\roslyn\csc.exe

Examples related to c#

Examples related to asp.net

Examples related to .net

Examples related to asp.net-mvc

Examples related to roslyn