Version 2
28.07.2011 09:50:58
Dies ist die aktuelle Version
Ich habe jetzt selbst eine Lösung gefunden (Internetrecherche):
try changing the [assembly: AssemblyVersion("1.0.*")] in AssemblyInfo.cs to [assembly: AssemblyVersion("1.0.0")] (i.e. without the "auto increment" asterisk for build/revision number). His suggestion to why this causes the problem, is "I'm guessing that VS was keeping a handle on each file it generated, so it would know how to increment things", which does sound at least plausible.
Bis jetzt ist das Problem nicht mehr aufgetaucht.
|
13,5k
●
3
●
9
|
Version 1
28.07.2011 09:46:57
Ich habe jetzt selbst eine Lösung gefunden (Internetrecherche):
try changing the [assembly: AssemblyVersion("1.0.*")] in AssemblyInfo.cs to [assembly: AssemblyVersion("1.0.0")] (i.e. without the "auto increment" asterisk for build/revision number). His suggestion to why this causes the problem, is "I'm guessing that VS was keeping a handle on each file it generated, so it would know how to increment things", which does sound at least plausible.
Bis jetzt ist das Problem nicht mehr aufgetaucht.
|
1,6k
●
8
|
