Assuming that there is a typo in your sources as DWright pointed out, I’d say that this error may arise just from the fact that by this code you define a static class MyModuleB with exposed method parameter of an external type MyCsharpType. This is how the Fsharp code translates to IL (from ILSpy – … Read more
Try getting the Build Logs, http://msdn.microsoft.com/en-us/library/vstudio/ms171470.aspx it seems that csc task could not find the source file. One cause it you import the wrong file. so you have to edit the project file via normal Text Editor.
This actually has nothing to do with config transforms. I just posted a very detailed blog at http://sedodream.com/2010/11/11/ASPNETWebApplicationPublishPackageTokenizingParameters.aspx. But some info here for you. In the Web Publishing Pipeline (WPP) we handle connection strings as special artifacts. We will automatically create parameters for you for all connection strings. This is because in many cases when … Read more
The first attempt failed because Package target doesn’t exist in the solution file. When using MSBuild on a solution file, a temporary MSBuild project is created (SamplePackage.sln.metaproj); this project file contains only some targets (Build, Clean, Rebuild, Publish, …) Solution : DeployOnBuild & DeployTarget properties One way to do what you want is to use … Read more
They are almost the same just as Daniel mentioned. The main difference is just as what you have found: Visual Studio Build step add Visual Studio Version to the build. Should I use the Visual Studio Build step or the MSBuild step? If you are building a solution, in most cases you should use the … Read more
Had the same problem and tried all sorts of values for /collection, finally hit the right one and all TFS2012 tf commands started working again. In Team Explorer in VS right click the server name and select properties, you need the entire URL parameter including http, the port number, everything. for me that was http://devserver:8080/tfs/defaultcollection … Read more
I encountered the same issue. The problem starts when you upgrade the DotNetCompilerPlatform to version 1.0.1. To work around this issue you can downgrade to version 1.0.0 using the NuGet package manager. EDIT: If you uninstall Microsoft.CodeDom.Providers.DotNetCompilerPlatform AND Microsoft.Net.Compilers, and then install the DotNetCompilerPlatform (has a dependency on the Microsoft.Net.Compilers package so it will automatically … Read more
To solve any of the following errors: “Failed building wheel for misaka” “Failed to build misaka” “Microsoft Visual C++ 14.0 is required” “Unable to find vcvarsall.bat” The solution is: Go to: https://www.visualstudio.com/downloads/#build-tools-for-visual-studio-2017 Select the free download under Visual Studio Community 2017 This will download the installer. Run the installer Now the most important step is … Read more