msbuild - Visual Studio 2015 UP1 always rebuilds my C# netmodule-output project. Can it be fixed? -


i have c# project, named 'x', modified x.csproj file, , changed <outputtype>library</outputtype> <outputtype>module</outputtype> means outputting .netmodule files instead of .dll files, cool, can use netmodules inputs c++/cli projects.

but, visual studio insists on recompiling project on every build, , when turn build output verbosity 'diagnostic', see line in output:

project 'x' not date. missing output file 'c:...\x\bin\debug\x.exe'.

the problem, of course, compiler outputting x.netmodule, , not x.exe, x.exe never found, , hence project recompiling on every build. worse, if run msbuild command line on csproj, correct behavior occurs, rebuilds when files within project have changed.

this leads me believe vs2015 [or others], computing final output name incorrectly because have specified module <outputtype>, , vs2015 forcing re-build, not msbuild.

i know modifying <outputtype> of .csproj non-standard, , not supported, seems method being using others bit, , seem known issue, possibly work-around.

thanks in advance.

okay, i'd love hear others have insight this, did come workaround. added copy command properties>build events>post-build event command line.

copy $(targetdir)$(targetname).netmodule $(targetdir)$(targetname).exe

this means when vs looks exe, (instead of .netmodule), find it, , has same date .netmodule, vs's logic whether re-build or not should corrected.


Comments

Popular posts from this blog

sql - VB.NET Operand type clash: date is incompatible with int error -

SVG stroke-linecap doesn't work for circles in Firefox? -

python - TypeError: Scalar value for argument 'color' is not numeric in openCV -