Hi,

I am using Visual Studio 2012 Ultimate Edition on Windows 8 Enterprise. Everything has been working smoothly, and all of a sudden I am facing a strange problem

None of my projects through Visual studio seem to build anymore. When I select Build solution, the build process starts but just locks up and stays in the "Build in progress" stage. Even if I create a new Visual Studio project (Metro App), Visual studio gets stuck on "Creating Project 'App1'" screen, and the output window just shows "Build started..."

I also have Visual Studio 2010 installed, but that works just fine and I am able to build my project.

I tried invoking the C# compiler in the command line, but that just locks up as well and doesn't show the help screen when invoked:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\csc.exe

(just hangs)

Also, if it helps, I am logging into my company domain and my user has full admin rights.

I am completely stuck on this, and any help would be appreciated. 

Thanks

Kunal

My Build fails as it is unable to find the Coded UI Testing tool references. When I build the same solution from Visual Studio, it builds fine with no issues.

I have created the solution\project in Visual Studio 2012. 

Another project, which was in Visual Studio 2010 builds successfully

I get the following error when I queue the build

I am getting the following error while using MSBuild: "error CS1606: Assembly signing failed; output may not be signed -- The process cannot access the file because it is being used by another process." This error sometimes occurs and sometimes doesn't while performing a build on the same code base. It also sometimes occurs and sometimes doesn't while using the underlying MS-DOS command. However, it does NOT occur while compiling within VS2005.  It also appears to be the SAME assembly.  Any ideas?

MSBuild Output:

Target MasterBuildAndDeploy:
        Target ActualBuild:
            "C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\IDE\devenv.exe" C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\BuildScripts\..\\Endurance.ESB.sln /Build Debug /Out "C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\BuildScripts\..\\Logs\Endurance.ESB.sln.log"
            C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\BuildScripts\Endurance.ESB.MGA.Build.Common.Targets(98,3): error MSB3073: The command ""C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\..\IDE\devenv.exe" C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\BuildScripts\..\\Endurance.ESB.sln /Build Debug /Out "C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\BuildScripts\..\\Logs\Endurance.ESB.sln.log"" exited with code 1.
        Done building target "ActualBuild" in project "Endurance.ESB.MGA.Build.General.proj" -- FAILED.
    Done building target "MasterBuildAndDeploy" in project "Endurance.ESB.MGA.Build.General.proj" -- FAILED.

VS Output:

------ Build started: Project: Endurance.ESB.Schemas, Configuration: Development .NET ------
Updating references...
Performing main compilation...
C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\Endurance.ESB.Common\Endurance.ESB.Schemas\MGA_Policy_Request_Envelope.xsd: warning BEC1006: Node "<Schema>" - The distinguished field 'IsValidated' might not exist in the schema.
C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\Endurance.ESB.Common\Endurance.ESB.Schemas\MGA_Policy_Request_XML.xsd: warning BEC1002: Node "EndorsementNumber" - Data type of this field or simple content record (xs:int) and the promoted property 'ns0:EndorsementNo' (xs:string) should be the same or they should map to the same CLR Type.
C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\Endurance.ESB.Common\Endurance.ESB.Schemas\MGA_Policy_Request_XML.xsd: warning BEC1002: Node "EndorsementNumber" - Data type of this field or simple content record (xs:int) and the promoted property 'ns0:EndorsementNumber' (xs:string) should be the same or they should map to the same CLR Type.
C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\Endurance.ESB.Common\Endurance.ESB.Schemas\MGA_Policy_Request_XML.xsd: warning BEC1005: Node "<Schema>" - The promoted field or simple content record 'ns1:IsValidated' might not exist in the schema.
C:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\Endurance.ESB.Common\Endurance.ESB.Schemas\PolicyTransactionsBatch.xsd: warning BEC1008: Node "PolicyTransactionsBatch" - Body XPath property is invalid or references a node that may not exist in the schema.
c:\Development\Workspaces\saugust\Endurance.Insurance.IITP\main\Endurance.ESB.Common\Endurance.ESB.Schemas\AssemblyInfo.cs(21,12): warning CS1699: Use command line option '/keyfile' or appropriate project settings instead of 'System.Reflection.AssemblyKeyFile'
error CS1606: Assembly signing failed; output may not be signed -- The process cannot access the file because it is being used by another process. 

Build complete -- 1 errors, 6 warnings 

Shawn (Mail@ShawnAugust.Com)

I am new to the concept of the .targets file.

I have set in my user properties file (Microsoft.Cpp.Win32.user.props) the IncludePath and LibraryPath, which works to add all the extra include path and library paths for my various VC++ projects.

Just wondering, rather than having it at the user level, is there a way to use the Microsoft.CppCommon.Targets file to set IncludePath and LibraryPath for all VC++ projects, all users on the machine?  Maybe through some property like "AdditionalIncludeDirectories" for header files, and "AdditionalDependencies" for .lib files to link?

I am not familiar with format of the .targets file to try and create the equivalent effect as the user properties settings I mentioned above:

<Project DefaultTargets="Build" ToolsVersion="4.0" ....>
  <PropertyGroup>
    <IncludePath>

and

<PropertyGroup>
    <LibraryPath>

Any feedback if what I am doing is possible in that targets file, and if so, how to add these types of entries would be a help.  Thanks.

After compile, I copy the Dll to a BinRef folder, from where other solutions refer a common dll.

I want this dll to be checked out automatically w/o the developer having the need to checkout manually. That way when there is a change in the Source, I copy the new Dll to binref and also check-it out automatically for the developer.

I want to check-out the dll in a smart way. In the AfterBuild task for a project, I want to know whether the project folder has any checkouts. If yes, I would checkout the dll copied to the bin folder.

I tried this command :

In my C++ source tree, I have a root directory with several *.vcxproj files used to build different subsets of projects in subdirectories:    all.vcxproj,   libraries.vcxproj, etc.

These root projects don't build anything, but they contain project references to those other projects.

With VS2013, I get the warning:

C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(381,5): warning MSB8028: The intermediate directory (x64\Debug\) contains files shared from another project (all.vcxproj).  This can lead to incorrect clean and rebuild behavior.

How can I avoid this warning?  Perhaps there is a way to define a *.vcxproj file that would include C++ project references yet not be based on CppBuild?  If so, could you please include an example?

Thanks.

Hello,

I am trying to build a solution that is checked out from Subversion. I opened the solution on a newly installed Visual Studio 2013. The solution has around 17 projects. The solution has Packages folder in it containing packages. When I try to build the solution all of failed. In the output window I see the error "Error occurred while restoring NuGet packages: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY))". I see that the Nuget Package Manager that came installed with VS 2013 has version 2.8.50313.46. I made sure that the package manager settings has the both the options "Allow NuGet to download missing packages" checked. I am new to VS 2013 and I don't have any clue or help from online forums. Please help me solve this.

I have c++ application that i cannot compile using Visual Studio 2013. When i try to compile i get following output:

I have a .wsdl file that I was able to add a config transformation to in Visual Studio 2010.  I converted that project to Visual Studio 2013, but now when I publish the .wsdl files are not being transform.  Looking at the publishing log I can see that the config transformation ran on the web.config, but none of the .wsdl files.

So on one of the .wsdl file I deleted all the config transformation thinking some link might be broken and that I would readd them and everything would be back to normal.  This didn't work as planned.  I don't see a "Add config transform" in the context menu when I right click on the .wsdl file in question.

So I have two questions, how do I get the transformation process to transform the .wsdl file that have already defined config transformation from Visual Studio 2010?  And how do I add the transformations to the .wsdl file that I deleted them from?  (I could undo changes from TFS, but I think if I can add them it will fix the first problem?)

Thanks for any insight.

I am doing a Copy task in the PostBuild Event.

And it is failing with error code 255.

<PostBuildEvent>

<Target Name="BeforeBuild">
  </Target>
  <Target Name="AfterBuild">
<Copy  SourceFiles="$(ProjectDir)$(OutDir)$(TargetFileName)"
  DestinationFolder="$(SolutionDir)Code\UI\Components\"
  SkipUnchnagedFiles="true"
  ContinueOnError="true"
  />
  </Target>

From other posts, I understand that, this happens when the file is not existing.

But if I take at the detailed error:

<Copy SourceFiles="C:\Source\Sandbox\DEVELOPMENT\bin\Debug\Proxy.dll" DestinationFolder="C:\Source\Sandbox\DEVELOPMENT\Client\Code\UI\Components\" SkipUnchnagedFiles="true" ContinueOnError="true" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" />" exited with code 255.

I made sure that the source file and the target folder are both existing and are full path.

What else could be the problem?

Note:

I don't want to use XCopy as I want to add an Exists() condition to this.

<Copy  SourceFiles="$(ProjectDir)$(OutDir)$(TargetFileName)"
  DestinationFolder="$(SolutionDir)Code\UI\Components\"
  Condition = "Exists($(SolutionDir)Code\UI\Components\)"
  SkipUnchnagedFiles="true"
  ContinueOnError="true"
  />

And I have to use Copy for that.

Thanks,

Sudheer

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

Hi All,

I have a requirement to check for some "BeforeBuild" criteria for each project in the solution.

I am having a custom task to test those criteria and I can modify each project file in the solution like this:

Hi everyone

all my [cs|vb]proj files import a custom targets file.  In here I want to override <DebugSymbols/> irrespective of which $(Configuration)|$(Platform) I am compiling.  (To save me the effort of setting it in every new project which gets created.)

I've tried setting this property inside and outside of a target in my custom targets file.

And I've tried tacking a target onto BeforeTargets="CoreCompile" - and setting it there.

In both cases it is getting set - as I can Message it out later.

What I want, of course is for CoreCompile to always set /debug:full when it constructs the call to [vbc|csc].exe.

But I just can't seem to get .pdbs if I set <DebugSymbols>false</DebugSymbols> in a projects's Release configuration.

Just can't seem to do it.

Anyone got any ideas, please?

N

Dear All,

 I have to convert an Exe to Dll using Visual Studio, how to do this?
 which version of visual studio is good for this? what are the features
should I look for achieving this?

can any one please help me soon...?

if this question is posted on wrong forum category, kindly someone change to correct forum category

Thank you in adavce...

Hi, I have a .NET application that is built using C++/CLI under Visual Studio 2012.  The main assemblies are built with 'safe' CLR support (/clr:safe) and hence correctly run as either a 32 or 64 bit application depending on target version of Windows.  i.e. target platofrm ='any'.  I'm starting to port for other languages and am able to create a satellite assembly for Japanese (for example) by adding a X.jp.resx resource file to the main assembly.  Visual Studio 2012 automatically creates the satellite assembly (X.resource.dll) however it sets the target platform to be x86, and hence it is not loaded when the application is run on an x64 platform.  It does this despite that fact that the parent assembly is set to target platform = 'any'.  I have been unable to locate the relevant project settings to enable the target platform for the satellite assembly to be set correctly.  Is anyone able to assist in clarifying where in Visual Studio these settings can be defined?  With thanks.

We recently upgraded for VS2010 to VS2013 and had to migrate over our dbproj to a sqlproj. Previously on Build of the main project of the solution the dbproj would also be deployed, however only the update script would be created (the changes would not be published). We did this through a targets file, that referenced the dbproj and did a deploy, with the properties on the dbproj set to only generate a script when deployed.

However on migrating to the new sqlproj this property no longer appears to be there. If we do a deploy using the targets file, only produces a dacpac file (we need a sql script) and if we do a publish, it creates the update script but then publishes it to the database. Is there a property that needs to be used on the publish to not update the database?

Here is the target file that I'm using:

<Projectxmlns="http://schemas.microsoft.com/developer/msbuild/2003">

 <PropertyGroup>

   <AfterAddContentPathToSourceManifestCondition="'$(AfterAddContentPathToSourceManifest)'==''">

     $(AfterAddContentPathToSourceManifest);

     DeployDbProjBeforePackage;

   </AfterAddContentPathToSourceManifest>

 </PropertyGroup>

 <!-- Specifies each dependent database project here, its properties will be appended to the target msbuild Properties-->

 <ItemGroup>

   <DBProjectInclude="..\Database\Database.sqlproj">

       <Properties>PublishScriptFileName=..\Database\sql\$(Configuration)\Database.sql</Properties>

       <Properties>SqlPublishProfilePath=..\Database\$(Configuration).publish.xml</Properties>

   </MyDependentDBProjects>

 </ItemGroup>

 <TargetName="DeployDbProjBeforePackage">

   <MessageText="Creating directory: %(DBProject.rootdir)%(DBProject.directory)sql\$(Configuration)" />

   <MakeDirDirectories="%(DBProject.rootdir)%(DBProject.directory)sql\$(Configuration)" />

   <MSBuildProjects="@(DBProject)"Targets="Build; Publish" />

 </Target>

</Project>

Hello...

     I've  build a Universal Windows DirectX Application and since I need some file inside my apps, I can't launch my application remotely (inside visual studio) on my Surface Pro (for touch test). I Need to create Windows Store Package, Transfer on network, Install on surface Pro and recopy all file at each time.

    The problem appends sometime on local machine and I need to rebuild twice to make it work. Presently I just use Post-Build event, but i will make a switch on Custom Step Build. Let make a resume.

You press F7 (build event was launch according thishttp://msdn.microsoft.com/en-us/library/e85wte0k.aspx)

1. Pre-Build event
2. Custom build tools on individual files
3. MIDL
4. Resource compiler
5. The C/C++ compiler
6. Pre-Link event
7. Linker or Librarian (as appropriate)
8. Manifest Tool
9. BSCMake
10. Custom build step on the project
11. Post-Build event

Release folder was create, but Appx was not. (Microsoft reality / base config)

My Post-Build eventhave create Appx (my reality / modified config)

Now you press F5 or CTRL-F5 (Appx folder was flushed)

I Regenerate and Post-Build event replace the file and everything go on (work local only)

Q: Does Custom event support Run function or it's just for build event. I've attempt to try with CleanAppxPackage event and seem to don't work. Some event in the custom step list seem work, but no one react on F5 or CTRL-F5 event.

I have a Web Site project on Visual Studio 2010. It used to generate ".compiled" file under "bin" folder. A couple days ago, it stopped to generate ".compiled" file. There isn't any error message on visual studio.

Folder "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files" is empty. Checked security of the folder, noticed ASP.Net user is not included.

Added full control permission of ASP.NET for the folder "Temporary ASP.NET files", pre-compiled file began to show up with folder name like "webhmi\3c83039e".

But ".precompiled" files are still not generated at "output\bin" folder. 

Added permission of ASP.net for source code folder did not help.

Then I tried to build and publish web site from virtual machine xp mode. ".compiled" files are generated.

Where should I investigate next step ? Is there any log file or trace file to look ?

Thanks.



Hi

My migration report says:

CommunityTalks.vcproj: All user macros reported below for configuration 'Debug (x64)|x64' are used before their definition, which can cause undesirable build results; this is not supported in this release. You can resolve this by changing the inclusion order of the consuming property sheets and making sure they come after the property sheets defining the user macros.
    CommunityTalks.vcproj: MSB4211: C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets (86,5); The property "TargetPlatformIdentifier" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Common.props (103,5)".
    CommunityTalks.vcproj: MSB4211: C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets (87,5); The property "TargetPlatformVersion" is being set to a value for the first time, but it was already consumed at "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Common.props (103,5)".

I don't know what to do ...

Andrew