Hi I have plenty of space on my machine.

ANd i have been using web deploy for a while.

but today I got this message. I know it should be some temp folder somewhere but I cannot find it!

any advice?

I have a C# class library project "“MyCompany.Framework.Logging" which has references to the following assemblies

1.       Microsoft.Practices.EnterpriseLibrary.Common.dll
2.       Microsoft.Practices.EnterpriseLibrary.Logging.dll
3.       Microsoft.Practices.EnterpriseLibrary.Data.dll
4.       Microsoft.Practices.EnterpriseLibrary.Logging.Database.dll

Then I have a another Web project which has project reference to “MyCompany.Framework.Logging”.

When I build the solution I see all 4 assemblies get copied to bin folder of ““MyCompany.Framework.Logging”,  However I see only the first 3 assemblies get copied to Web project’s bin folder but not the 4^th one (Microsoft.Practices.EnterpriseLibrary.Logging.Database.dll)

As per enterprise library forum

“Classes in assemblies that contain providers for an application block are typically not directly referenced, so the build process does not copy them as referenced binaries when building an application. Assemblies required by the application's configuration must be copied explicitly to the application's project output folder, either by adding explicit project references to them in the application project or as an ad-hoc post build step (recommended).”

So how do I copyMicrosoft.Practices.EnterpriseLibrary.Logging.Database.dll from bin folder of ““MyCompany.Framework.Logging” to  Web project’s bin folder in post build event?

I did build a "build customization" (.xml, .target, .props) for my own datatype... and it works if I compile the whole project. It also works if I clean the project, do incremental builds ... all these things work. Fine... but, when I right-click the file and select "compile" for just a single file... it executes the "clean" for my datatype and that's it... I can't find out why it is not executing the target that it executes when I build the complete project.

Can somebody tell me what's wrong? What should I do? Do you want to see the .targets file? Do you have a good example? Or is there something that you have to know and nobody ever wrote into a book? like e.g. "oh yes, in this case the 'Build' task is named 'DontBuild'" or something like that??

Rudolf

Hello,

After open my VS Ultimate 2012 C# solution in VS Ultimate 2013 12.0.21005.1REL I get the following warning:

Warning 1 Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190. EnergyMS

I follow the Microsoft link instructions. Then I edited the csproj file, adding the following line:

<AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>

When I build the solution again, I get the following error:

Error List
 "app.config;obj\x86\Debug\EnergyMS.csproj.EnergyMS.exe.config" is an invalid value for the "ConfigFile" parameter of the "GenerateApplicationManifest" task. Multiple items cannot be passed into a parameter of type "Microsoft.Build.Framework.ITaskItem". EnergyMS

Output Window:
C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(3243,9): error MSB4094: "app.config;obj\x86\Debug\EnergyMS.csproj.EnergyMS.exe.config" is an invalid value for the "ConfigFile" parameter of the "GenerateApplicationManifest" task. Multiple items cannot be passed into a parameter of type "Microsoft.Build.Framework.ITaskItem".

I've seen similar threads in fórum, but I don't understand the problem...

Can anyone help me understand the problem?

Thank you.

Hi,

I recently moved a solution  to a new build machine that uses a network share for the solution sources to be build. Before moving to the new machine everything worked fine when compiling the solutions using MSBuild. After moving I tried to build the code with MSBuild manually and got the error

Stdafx.cpp : fatal error C1192: #using failed on 'c:\buildsystem\build-dir\vsdk-vsdktt-tramx86\tram\plugins\exampleplugin\mscorlib.dll' [C:\buildsystem\build-dir\VSDK-VSDKTT-TRAMX86\TRAM\Plugins\ExamplePlugin\ExamplePlugin.vcxproj]

where 'build-dir' is a sym-link to \\server-ip\BuildShare$ created by 'mklink /d' from the command shell. The link is required as the build system is a service which seems to be unable to use a mapped network drive and which executes command shells which do not accept UNC paths as working directory.

The build machine is located within a domain network, the executing user is a domain network user without administration rights and full access to the share.

When copying the whole solution folder to the local hard disk and running the same msbuild command there, everything works fine. Compiling the solution within Visual Studio from the share also works fine.

After searching for the issue on the internet, I alrady tried:
* Adding the 'LoadFromRemoteSources' entry to the msbuild.exe.config
* Using CasPol.exe to fully trust the server share
* Adding the server to the 'Local intranet' in the internet options and lowering the security there to level 'Low'
* Mapping the network share to drive Z: and redirecting the sym-link there

but the problem still persists.

Versions:
MSBuild Version: 12.0
Visual Studio Version: VS2013 Upgrade 1
The project causing the error is a .NET C++/CLI DLL.

Has anybody got an idea how to make the solution compile from the network share?
Thanks for your help,

Thomas

Is it possible to run MTM Test Controllers and Agents using RSA Authentication? I have not been able to find any info on the net related to RSA and MTM limitations. I suspect that RSA & MTM are not playing well together. If this is the problem does anyone know of a possible work around? I am using a Standard Environment.

I am trying to set up a test controller/agent combination using 2012 MTM but I cannot get the Environment to Start. It appears that everything is configured correctly; however, when the VM with the controller/agent attempts to restart I encounter the error messages below and the Environment Status states that it is “Not Ready”.

Environment message: Type=Error; Message=TF259098: Team Foundation Server could not perform the following operation because of errors on one or more virtual machines: Update environment. Resolve those errors, and then try the operation again.;

Machine messages: Machine name: SPF43Dev01 Machine message: Type=Error; Message=Microsoft Test Manager could not complete the following action: Validating the user name and password for coded UI tests. Additional information: TF260948: The user name or password provided to configure the test agent to run as a process are not valid.

Error code: 1326;

Hi,

I'm building my installshield 2013 project using MSBuild and it is not including all the dependent dlls in the setup.exe. When i build the same solution using visual studio 2012 everything works fine and all dependent dlls are included in the setup file.

Regards,

Maaya.

While using Visual Studio for many years, I didn't have an experience with manual invocation of MSBuild until recently, when trying to figure out why Studio cannot build a solution — only to find out that MSBuild proceeds seamlessly rather than outputs detailed error messages. While digging up more and more, it became apparent that some project description styles that are perfectly accepted by MSBuild are totally incompatible with IDE. As I'm not a CLI guru, I would like to find out what am I possibly missing and how to achieve the same results within GUI.

Issue 1. Configuration manager in Visual Studio 2012 IDE doesn't seem to recognize project configurations and platforms defined withCondition attribute of When statements of Choose-When-Otherwise blocks.

<Choose><When Condition=" '$(Configuration)' == 'Debug' "><PropertyGroup><TargetFrameworkVersion>v4.5</TargetFrameworkVersion><DefineConstants>dotNet=4.5, HaveTesting=True, HaveDumper=True</DefineConstants></PropertyGroup></When><When Condition=" '$(Configuration)' == 'RlzFull' "><PropertyGroup><TargetFrameworkVersion>v4.5</TargetFrameworkVersion><DefineConstants>dotNet=4.5, HaveTesting=False, HaveDumper=True</DefineConstants></PropertyGroup></When><When Condition=" '$(Configuration)' == 'RlzLite' "><PropertyGroup><TargetFrameworkVersion>v3.5</TargetFrameworkVersion><TargetFrameworkProfile>Client</TargetFrameworkProfile><DefineConstants>dotNet=3.5, HaveTesting=False, HaveDumper=False</DefineConstants></PropertyGroup></When></Choose><Choose><When Condition=" '$(Configuration)' == 'Debug' "><PropertyGroup><DebugType>full</DebugType><DebugSymbols>true</DebugSymbols><DefineDebug>true</DefineDebug><DefineTrace>true</DefineTrace></PropertyGroup></When><Otherwise><PropertyGroup><DebugType>none</DebugType><DebugSymbols>false</DebugSymbols><DefineDebug>false</DefineDebug><DefineTrace>false</DefineTrace></PropertyGroup></Otherwise></Choose><Choose><When Condition=" '$(Platform)' == 'AnyCPU' "><PropertyGroup><PlatformTarget>AnyCPU</PlatformTarget><Prefer32Bit Condition=" $(TargetFrameworkVersion.Substring(1)) &gt;= 4.5 ">true</Prefer32Bit></PropertyGroup></When><When Condition=" '$(Platform)' == 'x86' "><PropertyGroup><PlatformTarget>x86</PlatformTarget></PropertyGroup></When><When Condition=" '$(Platform)' == 'x64' "><PropertyGroup><PlatformTarget>x64</PlatformTarget></PropertyGroup></When></Choose>

For such a project, Configuration manager displays “Debug” and “Any CPU” (not “AnyCPU”!) as the only defined. However, when trying to define “x86” again, an error message appears saying that this item already exists.

Issue 2. If switching configurations requires .NET version change, IDE is totally screwed. Consider the following project description, which is simply an IDE-compatible variant of the same listing as above (less legible, isn't it?).

<PropertyGroup Condition=" '$(Configuration)' == 'Debug' "><TargetFrameworkVersion>v4.5</TargetFrameworkVersion><DefineConstants>dotNet=4.5, HaveTesting=True, HaveDumper=True</DefineConstants></PropertyGroup><PropertyGroup Condition=" '$(Configuration)' == 'RlzFull' "><TargetFrameworkVersion>v4.5</TargetFrameworkVersion><DefineConstants>dotNet=4.5, HaveTesting=False, HaveDumper=True</DefineConstants></PropertyGroup><PropertyGroup Condition=" '$(Configuration)' == 'RlzLite' "><TargetFrameworkVersion>v3.5</TargetFrameworkVersion><TargetFrameworkProfile>Client</TargetFrameworkProfile><DefineConstants>dotNet=3.5, HaveTesting=False, HaveDumper=False</DefineConstants></PropertyGroup><PropertyGroup	Condition=" '$(Configuration)' == 'Debug' "><DebugType>full</DebugType><DebugSymbols>true</DebugSymbols><DefineDebug>true</DefineDebug><DefineTrace>true</DefineTrace></PropertyGroup><PropertyGroup Condition=" '$(Configuration)' != 'Debug' "><DebugType>none</DebugType><DebugSymbols>false</DebugSymbols><DefineDebug>false</DefineDebug><DefineTrace>false</DefineTrace></PropertyGroup><PropertyGroup Condition=" '$(Platform)' == 'AnyCPU' "><PlatformTarget>AnyCPU</PlatformTarget><Prefer32Bit Condition=" $(TargetFrameworkVersion.Substring(1)) &gt;= 4.5 ">true</Prefer32Bit></PropertyGroup><PropertyGroup Condition=" '$(Platform)' == 'x86' "><PlatformTarget>x86</PlatformTarget></PropertyGroup><PropertyGroup Condition=" '$(Platform)' == 'x64' "><PlatformTarget>x64</PlatformTarget></PropertyGroup>

As previously, MSBuild compiles this just fine, but after switching from “Debug” (.NET 4.5) to “RlzLite” (.NET 3.5) in Visual Studio IDE and trying to build the solution all we get will be a 100+ error messages per project.

The build output log shows that the very first project (LibUtil.dll) is successfully compiled. However, when inspecting the built assembly, it can be seen that it referencesmscorlib.dll4.0.0.0 and System.dll2.0.0.0, — which makes no sense. When built manually, both referenced libraries are of version 2.0.0.0 for the .NET 3.5 configuration and of version 4.0.0.0 for the .NET 4.5 configuration, — as expected.

All subsequent projects have a bunch of similar errors in the log:

error BC30002: Type 'FooClass.BarClass' is not defined.
error BC30451: 'FooClass' is not declared. It may be inaccessible due to its protection level.
……………
warning MSB3258: The primary reference "...\LibUtil.dll" could not be resolved because it has an indirect dependency on the .NET Framework assembly "System.Windows.Forms, Version=4.0.0.0, ..." which has a higher version "4.0.0.0" than the version "2.0.0.0" in the current target framework.
……………
warning MSB3268: The primary reference "...\LibUtil.dll" could not be resolved because it has an indirect dependency on the framework assembly "System.Web.ApplicationServices, Version=4.0.0.0, ..." which could not be resolved in the currently targeted framework.

Note the warnings: for a simple library project that actually references System andSystem.Core only, the log states that it references several dozens of .NET libraries: Accessibility, ComponentModel.DataAnnotations, Configuration.Install, Data.OracleClient, Deployment, DirectoryServices, Drawing, EnterpriseServices, Management, Microsoft.JScript, Runtime.Caching, Transactions, Web.ApplicationServices, Windows.Forms, etc. What do all these have to do with my projects?

As if it were not enough, it turned out that switching configuration that results in .NET version change may crash Visual Studio IDE: after I switched to “RlzLite” which produced compilation errors listed above, I could not return back to working “Debug”, because IDE crashed on each attempt. Only after I unloaded all projects except the simplest one, I was able to switch configuration and then to reload other projects.

So, to summarize my questions.

1. Is Visual Studio [2012] IDE deliberately inferior in understanding project descriptions that are fine for MSBuild? If so, how it is possible to understand from documentation which syntax options are not supported by IDE?
2. Is it possible to switch between different .NET versions inside IDE, or do I have to re-target each project manually as I did earlier with a single project?

Of course, the easiest way would be to use IDE for “Debug” configuration only and build other versions manually, but this would have a major disadvantage of not being able to easily observe source code errors in conditional compilation blocks and those inherent to .NET version differences, — for me this is a show-stopper: I'm not that skilled to “develop with Notepad”. :-)

The error says:

error LNK2019: unresolved external symbol WinCPUID_Init referenced in function "public: static void __cdecl CCapturer::GetCPUVendorId(void)" (?GetCPUVendorId@CCapturer@@SAXXZ)

but it doesn't point out which lib I should add in MSDN.

How to solve it ?

I am trying to use an example to use a custom app_offline during web deploy. The  example can be found at:

http://sedodream.com/2012/01/08/HowToTakeYourWebAppOfflineDuringPublishing.aspx

My problem is that the msdeploy command that is generated correctly set authentication=basic but does not include a password.  I am using an IIS Manager account when I try to publish the site. 

Without the wpp.targets file it publishes fine.

If I copy the generated msdeploy command and add password='mypassword'   the command runs fine.

How can I force the pipeline to include the password?

Examples and documentation seems few and far between.

Hello,

I have project Test.csproje. File config.xml includesd in this project. TFS build configuration with default template

Config.xml file:

<DBConfig>
  <ConnectionStrings>
    <ConnectionString name="XXXXXXX" server="YYYYYY" database=ZZZZZZZ">
      <DBPurpose name="DDDDD">Integrated Security=SSPI; Application Name=CCCCC; Packet Size=4096;Data Source=BBBBB;Initial Catalog=AAAAA; Persist Security Info=False;Asynchronous Processing=true;</DBPurpose>
    </ConnectionString>
  </ConnectionStrings>
</DBConfig>

I want to set parameters, who depends on build configuration. for example /p:VariableValue=Test or parameter depends on project configuration Debug, UAT, Release.

If I wrote in csproj - build doesn't see $(VariableValue)inconfig.xml

  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
    <VariableValue>\Test</VariableValue>
  </PropertyGroup>

config.xml

<DBConfig>
  <ConnectionStrings>
    <ConnectionString name="$(VariableValue)" server="$(VariableValue)" " database=$(VariableValue)" ">
      <DBPurpose name="DDDDD">Integrated Security=SSPI; Application Name=CCCCC; Packet Size=4096;Data Source=BBBBB;Initial Catalog=AAAAA; Persist Security Info=False;Asynchronous Processing=true;</DBPurpose>
    </ConnectionString>
  </ConnectionStrings>
</DBConfig>

And when I build my Test.csproje with MSBUILD i have file

<DBConfig>
  <ConnectionStrings>
    <ConnectionString name="Test" server="Test" database=Test">
      <DBPurpose name="DDDDD">Integrated Security=SSPI; Application Name=CCCCC; Packet Size=4096;Data Source=BBBBB;Initial Catalog=AAAAA; Persist Security Info=False;Asynchronous Processing=true;</DBPurpose>
    </ConnectionString>
  </ConnectionStrings>
</DBConfig>

How can I do it?

Hi,

I want to execute a powershell script as post build step.

When I add a

powershell.exe "Write-Host PostBuildStep"

this is working and I see the output.

but putting:

powershell.exe $(SolutionDir)powershellscript.ps1

there is an error:

  File D:\SVN\Solution\powershellscript.ps1 cannot be loaded because the execution of scripts is disabled on this sys
  tem. Please see "get-help about_signing" for more details.
  At line:1 char:71+ D:\SVN\Solution\powershellscript.ps1 <<<< + CategoryInfo          : NotSpecified: (:) [], PSSecurityException+ FullyQualifiedErrorId : RuntimeException

I already opend a Powershell console as administrator and executed 'Set-ExecutionPolicy Unrestricted'.
Entering as normal user (which is also running VisualStudio) 'Set-ExecutionPolicy' returns Unrestricted.

But the error still persists.

What could be the problem?

Hi I am using VS2010

My requirement is that I want some code snippet or API (if so)  to detect the insertion of Media or Removal of Media along with drive letter without using any window class...

Say I have already implemented using ShellNotifyRegister function and as well Wndproc function for getting window messages in both cases I have to register a window class.

But Please help to detect media ( specially USB ) in console application of VS2010 without registering a window class.

Do we get some API ?

renukumarisharma

Hi!

We deploy one of our projects by webdeploy 3.5. We noticed that after installing AppFabric 1.1  we get an error when deploying:

Hi,

I have an application. I don't have any build errors. But when I try to launch the application, its closing when its about to launch. I saw below messages in output window.

 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities\12.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089\System.Windows.Forms.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Drawing\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.HostingProcess.Utilities.Sync\12.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.HostingProcess.Utilities.Sync.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.Debugger.Runtime\12.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Debugger.Runtime.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'vshost.exe'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'Microsoft.Practices.Prism.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded '\Microsoft.Practices.Unity.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_32\PresentationCore\v4.0_4.0.0.0__31bf3856ad364e35\PresentationCore.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\WindowsBase\v4.0_4.0.0.0__31bf3856ad364e35\WindowsBase.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\PresentationFramework\v4.0_4.0.0.0__31bf3856ad364e35\PresentationFramework.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Data.DataSetExtensions\v4.0_4.0.0.0__b77a5c561934e089\System.Data.DataSetExtensions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Deployment\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Deployment.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Design\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Design.dll'. Cannot find or open the PDB file.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Management.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceProcess\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Extensions\v4.0_4.0.0.0__31bf3856ad364e35\System.Web.Extensions.dll'. Cannot find or open the PDB file.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xaml\v4.0_4.0.0.0__b77a5c561934e089\System.Xaml.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml.Linq\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.Linq.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
 : Loaded 'ApplicationFramework.Core.Logging.dll'. Symbols loaded.
 : Loaded ' Symbols loaded.
 : Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\WindowsFormsIntegration\v4.0_4.0.0.0__31bf3856ad364e35\WindowsFormsIntegration.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
The thread 0x33d4 has exited with code 259 (0x103).
The thread 0x18d4 has exited with code 0 (0x0).
The thread 0x23b8 has exited with code 0 (0x0).
The thread 0x1254 has exited with code 259 (0x103).
 : Loaded '. Symbols loaded.
 : Loaded ''. Symbols loaded.
 : Loaded ''. Symbols loaded.
The program 'vshost.exe' has exited with code -1073740771 (0xc000041d).

I've just migrated my solution (~300 projects) from vs2010 to vs2012, the solution is a mix of unmanaged C\C++, managed C\C++, and C# projects.

My solution would build in 2010, but in 2012, I cannot

Save anything

Clean anything

Build anything

Add a reference to any projects

Without getting the error `The project file ' ' has been renamed or is no longer in the solution` in C++, and 'The operation could not be completed, the parameters are incorrect.'.

After scouring the nets, the general consensus is that 'I have a bad reference somewhere' check your project references.  This is totally unweildy given the size of my solution.  I spent a few hours going through an initial pass, and didn't find any missing.

If the problem IS indeed that I have bad references, is there any type of tool I could be using to find the specific problems?

Not to be a classic complainer, but:
If my team gets upgraded to vs2012, and this error shows up on a developers machine, saying 'check every reference in every project' is not an acceptable solution. I'm going to have to hold off until I can get some concrete information about this error.

echo set WshShell = WScript.CreateObject("WScript.Shell") > %tmp%\tmp.vbs

echo WScript.Quit (WshShell.Popup( "The system will shutdown in 15 minutes, Click OK to ABORT !!" , 900 ,"Shutdown", 0)) >> %tmp%\tmp.vbs

cscript /nologo %tmp%\tmp.vbs
 del %tmp%\tmp.vbs

\m/

We have a C# solution in VS2012 for which we have added post-build steps to copy the resulting DLLs to another folder.  The individual projects build fine, and selecting "Build All" after a failed "Rebuild All" also works fine, but when rebuilding the entire solution, different projects fail on the post-build step, and it seems random and not at all consistent.  The errors we get are always of this nature:

     Error 1  The command "copy C:\IP\Common\IPDBContext\bin\Debug\*.dll C:\IP\SharedCommon /y" exited with code 1.

The post-build steps all look like this:

     copy $(ProjectDir)$(OutDir)*.dll C:\IP\SharedCommon /y

Can anyone provide clues as to why this randomly fails?

Thanks,

Peter