Use " to encode the double quotes that you want net to see inside the Command attribute value : <Exec Command=”net use x: "\\ofmapoly703\c$\program files\ar\iap" /user:$(UserID) $(Password)” WorkingDirectory=”c:\” ContinueOnError=”false” />
The projects you are trying to open are in the new .NET Core csproj format. This means you need to use Visual Studio 2017 which supports this new format. For a little bit of history, initially .NET Core used project.json instead of *.csproj. However, after some considerable internal deliberation at Microsoft, they decided to go … Read more
It turns out the trailing slash in the PublishDir property is escaping the end quote. Escaping the trailing slash solved my problem. /p:PublishDir=”\\BSIIS3\c$\DATA\WEBSITES\benesys.net\benesys.net\TotalEducationTest\\” This way we can use quotes for paths that have whitespace in properties that MSBuild requires the trailing slash. I know this is an old post, but I feel like I needed … Read more
By dynamically linking with /MD, you are exposed to system updates (for good or ill), your executable can be smaller (since it doesn’t have the library embedded in it), and I believe that at very least the code segment of a DLL is shared amongst all processes that are actively using it (reducing the total … Read more
I didn’t look very well, there’s another property added to the project files: <RestorePackages>true</RestorePackages> Just have to remove this as well as all these lines manually from all *.csproj files: <Import Project=”$(SolutionDir)\.nuget\nuget.targets” /> UPDATE: Turns out it’s a persistent little bugger, if you’re manually editing your project files, make sure to close the solution and … Read more
You can add this to a <PropertyGroup> inside your csproj file to enforce copying NuGet assemblies to the build output: <CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies> However, note that the build output (bin/Release/netcoreapp*/*) is not supposed to be portable and distributable, the output of dotnet publish is. But in your case, copying the assemblies to the build output is probably … Read more
The Private tag maintains the user-override to the “Copy Local” checkbox in the Visual Studio References folder. This controls whether the reference is used from the GAC or whether it will copy the referenced assembly to the build directory. While I cannot find any MSDN documentation to this effect (quelle surprise), it is evident from … Read more
I’m not sure what causes it, but restarting VS 2012 fixed it for me.
In a previous project I worked with one big solution with project references and bumped into a performance problem as well. The solution was three fold: Always set the Copy Local property to false and enforce this via a custom msbuild step Set the output directory for each project to the same directory (preferably relative … Read more
I’ve done a similar investigation this week. Here’s what I’ve been able to determine: NAnt: Cross-platform (supports Linux/Mono). It may be handy for installing a web site to multiple targets (that is, Linux Apache and Windows IIS), for example. 95% similar in syntax to Ant (easy for current Ant users or Java builders to pick … Read more