csc

问题 I have error in my project on time of build csc.exe exited with code -2146232797 visual studio 2017(Professional) in other Team's computer project building and running fine, so I not want to update nuget compiler, Is there any permanent solutions there? 回答1: This issue happened for some people with vs 2017. you need to reinstall .net via microsoft site as requested and if the above link does not help, there is a thread in visual studio development community stating they fixed the issue in

问题 I have error in my project on time of build csc.exe exited with code -2146232797 visual studio 2017(Professional) in other Team's computer project building and running fine, so I not want to update nuget compiler, Is there any permanent solutions there? 回答1: This issue happened for some people with vs 2017. you need to reinstall .net via microsoft site as requested and if the above link does not help, there is a thread in visual studio development community stating they fixed the issue in

问题 When compiling my solution, I get several warnings of the following: warning CS3016: Arrays as attribute arguments is not CLS-compliant No other information on what type is not compliant is given. In my projects I have some attributes that take params array arguments in their constructors, but they are all internal, and that shouldn't affect CLS-compliance. Why is this warning being given, and what type is it being given on? 回答1: CS3016. If you have an attribute which takes an array as

问题 I am trying to make a simple c# program using Growl C# API . I tried to compile my program in two different ways: 1) I kept my .dll file in the same directory as my .cs file. Than I ran csc /r:Growl.Connector.dll,Growl.CoreLibrary.dll /out:test.exe *.cs It compiled fine and also ran fine. 2) Now I have created a directory inside my current working directory named growl and kept all my .dll references there. Now when I try to compile it using the below command csc /r:"D:\Modified\Growl_NET

问题 Is there a way to get path for the latest .NET Framework's csc.exe? The file usually in: c:\Windows\Microsoft.NET\Framework\vX.X.XXX but the problem is there can be multiple versions installed + there are both 32 and 64 bit versions. Any solution to this? 回答1: c:\Windows\Microsoft.NET\Framework\vX.X.XXX Should contain the latest 32 bit version of csc.exe c:\Windows\Microsoft.NET\Framework64\vX.X.XXX Should contain the lastest 64 bit version of csc.exe That's what it is for mine anyway. BTW:

问题 Is there a way to get path for the latest .NET Framework's csc.exe? The file usually in: c:\Windows\Microsoft.NET\Framework\vX.X.XXX but the problem is there can be multiple versions installed + there are both 32 and 64 bit versions. Any solution to this? 回答1: c:\Windows\Microsoft.NET\Framework\vX.X.XXX Should contain the latest 32 bit version of csc.exe c:\Windows\Microsoft.NET\Framework64\vX.X.XXX Should contain the lastest 64 bit version of csc.exe That's what it is for mine anyway. BTW:

问题 I have a C# solution and some referenced dll-s. Even though when compiling in visual studio(vs2010) it appears as it succeeded, when using the C# compiler it fails: missing dll apparently.. csc /t:library /out:test.dll test.cs test.cs(22,10): error CS0246: The type or namespace name 'Attribute' could not be found (are you missing a using directive or an assembly reference?) Does anyone know why is this happening? 回答1: As you haven't given the code, it's not clear what type Attribute is meant

问题 I have a C# solution and some referenced dll-s. Even though when compiling in visual studio(vs2010) it appears as it succeeded, when using the C# compiler it fails: missing dll apparently.. csc /t:library /out:test.dll test.cs test.cs(22,10): error CS0246: The type or namespace name 'Attribute' could not be found (are you missing a using directive or an assembly reference?) Does anyone know why is this happening? 回答1: As you haven't given the code, it's not clear what type Attribute is meant

问题 I was using Visual studio 2013. Yesterday, I installed VS2015(enterprise update 3). The build process for my solution crashes in VS2015 for one of the projects. The same exception occurs with VS2017 RC. The solution was building succesfully in VS2013. The solution is targeting .Net4.5. When I migrate to .Net4.6.2, it does not solve this issue. I believe the problem is coming with compiler included in VS2015+ Output : Process is terminated due to StackOverflowException. C:\Program Files (x86)

问题 After switching to Visual Studio 2015, we have noticed that some changes made to how lambdas are compiled to MSIL in Roslyn (described in this thread and on GitHub) introduce runtime failures under certain conditions. Since Roslyn is obviously the future of .NET, we would like to switch to this technology, but it seems that all legacy code which has been running in production (and where we have a fair degree of confidence it works correctly) is now prone to new runtime failures. These are