Quantcast
Channel: MSBuild forum
Viewing all 2763 articles
Browse latest View live

MSBuild and multiple post deploy sql script

$
0
0

All,

We implemented CI/CD via DevOps on Azure against our on-prem SQLServers. Most of the changes are DDL changes to Tables, View, SP and Functions.

We would like to implement data zaps (DML) which we are currently accomplishing using sql script files. We tried to implement the same via the Post-Deploy script file but though this technique works it has an inherent limitation of just one post deploy script. Even though we can list multiple sql files at design time at build time it takes the content of each of these files and appends them one below the other.

The problem starts when one of the script errors out. Even though it does give the complete message it does not mention which script file the error originated from. This becomes an issue when we have multiple DML script files with each of them having hundreds of lines of code.

Is there a setting in sqlproj file or some option in MSBuild that would help us specify better config option for these DML scripts and their execution?

I’m looking for a way to make the deploy utility – sqlpackage.exe list the sql file the error originated from apart from the line number and the actual error message.

Thanks,

rgn


angular project: The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

$
0
0

I have an Angular project (ASP.NET Core over .NET 4.6) built with VS2017. Project is ok, but I cannot release and publish it because build reports:

Unable to copy file "D:\Source.Git\AAAAAAAA\AAAA.AAAAAAA.Web\ClientApp\node_modules\.cache\uglifyjs-webpack-plugin\content-v2\sha512\20\4f\50f5067a85b2475f2b212c7eeccf1a529464a2f4a71dea4f363200f72d40aa09ccdcf9b1452c0e27792882b51a53fcc2778d1801292dbef940725b12a7ab" to "D:\Source.Git\AAAAAAAA\AAAA.AAAAAAAWeb\obj\Release\net462\win7-x86\PubTmp\Out\ClientApp\node_modules\.cache\uglifyjs-webpack-plugin\content-v2\sha512\20\4f\50f5067a85b2475f2b212c7eeccf1a529464a2f4a71dea4f363200f72d40aa09ccdcf9b1452c0e27792882b51a53fcc2778d1801292dbef940725b12a7ab". The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

I tried to copy solution (as workaround, not a solution available) to Z:\a\ but same. Tried to enable long file paths in W10 via regedit but VS 2017 ignores it. Tried npm flatten packages. Nothing.

I cannot change npm modules, nor I cannot change VS internal paths! So how can an Angular project built with VS released?????

MSBuild in VSTS

$
0
0

I am currently building a Build pipeline for a xamarin project, i am currently getting the following error on building the android project in VSTS. Any help will do

\MSBuild\Xamarin\Android\Xamarin.Android.CSharp.targets" was not found

ASP .NET web application publishing failure

$
0
0

I am trying to publish my ASP.NET web application to a web server using ftp method.

However when I try to publish the method method, It built successfully but publishing failed with following warnings:

1.Imported schema for namespace 'urn:schemas-microsoft-com:asm.v1' was not resolved.

2.The global element 'configuration' has already been declared.

I have followed different solution available across different forum. But none of them come helpful.I am using visual studio 2017. please someone help

Solution with multiple web application projects

$
0
0

We have a solution with multiple web applications, and we are having a problem with the desired package being overwritten when running a build in an Azure DevOps pipeline. We are currently running a build task on the solution and passing the following MSBuild paramaters.

/p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:PackageLocation="$(build.artifactstagingdirectory)\\$(appName).zip"

We have some possible solutions that are yet to be tested.

  1. Validate the solution places the web application project for the desired package as the last web application in the project build order list. (downside: multiple packages are still created, using unnecessary processing time)
  2. Run the build on the solution without the publish/package parameters, then follow up with a project build using the publish/package parameters.

We have future efforts toward implementing package management, which should help address the multiple-web-applications-per-solution structure. Until that occurs, is there a "correct" way to specify to the MSBuild execution that a single package is desired, and the project from which that package should be generated?


James Bristow, Software Configuration Manager

Adding basic property makes project consuming winmd fail to build -- error MSB4018

$
0
0

This issue has been popping up regularly. it only happens when building Windows Run TimeComponent (not DLL) then attempt to consume it in another UWP project.

It seems like a important file in our winmd goes into a semi locked state. Where if i add a innocuous property that it not referenced by anything like:

public string SelectedNode2 { get; set; }

the winmd builds, but it will not let the app that consumes the winmd build. It spits out a huge error below:

commenting out the prop lets everything work again. 

The only way i've seen this issue go away (i think) is Reparing VisualStudio. But that takes an hour, and it didn't seem to work last time.

Has anyone found a way to clear this error???? Seems like a VS bug somehow. It appear that the complier is expecting a set number of strings/properties and if i add an additional one it pukes. Commenting out a different string and bring back the other one makes it work again. 

ErrorTask 'GenerateAppxManifest' failed. Object reference not set to an instance of an object. 

followed by this huge error:

SeverityCode DescriptionProjectFileLineSuppression State
ErrorThe "GenerateAppxManifest" task failed unexpectedly.
System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(IMetadataExpression expression)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(IMetadataNamedArgument namedArgument)
   at Microsoft.Cci.MetadataTraverser.Traverse(IMetadataNamedArgument namedArgument)
   at Microsoft.Cci.MetadataTraverser.Traverse(IEnumerable`1 namedArguments)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(ICustomAttribute customAttribute)
   at Microsoft.Cci.MetadataTraverser.Traverse(ICustomAttribute customAttribute)
   at Microsoft.Cci.MetadataTraverser.Traverse(IEnumerable`1 customAttributes)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(ITypeDefinitionMember typeMember)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(IMethodDefinition method)
   at Microsoft.Cci.MetadataTraverser.Traverse(IMethodDefinition method)
   at Microsoft.Cci.MetadataTraverser.Traverse(IEnumerable`1 methods)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(ITypeDefinition typeDefinition)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(INamedTypeDefinition namedTypeDefinition)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(INamespaceTypeDefinition namespaceTypeDefinition)
   at Microsoft.Cci.MetadataTraverser.Traverse(INamespaceTypeDefinition namespaceTypeDefinition)
   at Microsoft.Cci.MetadataTraverser.Dispatcher.Visit(INamespaceTypeDefinition namespaceTypeDefinition)
   at Microsoft.Cci.MetadataReader.ObjectModelImplementation.NamespaceType.Dispatch(IMetadataVisitor visitor)
   at Microsoft.Cci.MetadataTraverser.Traverse(IEnumerable`1 namespaceMembers)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(INamespaceDefinition namespaceDefinition)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(IUnitNamespace namespaceDefinition)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(INestedUnitNamespace nestedUnitNamespace)
   at Microsoft.Cci.MetadataTraverser.Traverse(INestedUnitNamespace nestedUnitNamespace)
   at Microsoft.Cci.MetadataTraverser.Dispatcher.Visit(INestedUnitNamespace nestedUnitNamespace)
   at Microsoft.Cci.MetadataReader.ObjectModelImplementation.NestedNamespace.Dispatch(IMetadataVisitor visitor)
   at Microsoft.Cci.MetadataTraverser.Traverse(IEnumerable`1 namespaceMembers)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(INamespaceDefinition namespaceDefinition)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(IUnitNamespace namespaceDefinition)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(INestedUnitNamespace nestedUnitNamespace)
   at Microsoft.Cci.MetadataTraverser.Traverse(INestedUnitNamespace nestedUnitNamespace)
   at Microsoft.Cci.MetadataTraverser.Dispatcher.Visit(INestedUnitNamespace nestedUnitNamespace)
   at Microsoft.Cci.MetadataReader.ObjectModelImplementation.NestedNamespace.Dispatch(IMetadataVisitor visitor)
   at Microsoft.Cci.MetadataTraverser.Traverse(IEnumerable`1 namespaceMembers)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(INamespaceDefinition namespaceDefinition)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(IUnitNamespace namespaceDefinition)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(INestedUnitNamespace nestedUnitNamespace)
   at Microsoft.Cci.MetadataTraverser.Traverse(INestedUnitNamespace nestedUnitNamespace)
   at Microsoft.Cci.MetadataTraverser.Dispatcher.Visit(INestedUnitNamespace nestedUnitNamespace)
   at Microsoft.Cci.MetadataReader.ObjectModelImplementation.NestedNamespace.Dispatch(IMetadataVisitor visitor)
   at Microsoft.Cci.MetadataTraverser.Traverse(IEnumerable`1 namespaceMembers)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(INamespaceDefinition namespaceDefinition)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(IUnitNamespace namespaceDefinition)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(INestedUnitNamespace nestedUnitNamespace)
   at Microsoft.Cci.MetadataTraverser.Traverse(INestedUnitNamespace nestedUnitNamespace)
   at Microsoft.Cci.MetadataTraverser.Dispatcher.Visit(INestedUnitNamespace nestedUnitNamespace)
   at Microsoft.Cci.MetadataReader.ObjectModelImplementation.NestedNamespace.Dispatch(IMetadataVisitor visitor)
   at Microsoft.Cci.MetadataTraverser.Traverse(IEnumerable`1 namespaceMembers)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(INamespaceDefinition namespaceDefinition)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(IUnitNamespace namespaceDefinition)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(IRootUnitNamespace rootUnitNamespace)
   at Microsoft.Cci.MetadataTraverser.Traverse(IRootUnitNamespace rootUnitNamespace)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(IModule module)
   at Microsoft.Cci.MetadataTraverser.TraverseChildren(IAssembly assembly)
   at Microsoft.Cci.MetadataTraverser.Traverse(IAssembly assembly)
   at Microsoft.Build.AppxPackage.WinmdVisitor.Traverse(IAssembly assembly, Boolean swallowTraversalException)
   at Microsoft.Build.AppxPackage.WinmdVisitor.Traverse(DefaultHost host, Boolean swallowTraversalException)
   at Microsoft.Build.AppxPackage.WinmdVisitor.ProcessInternal(AppxPackagingTaskHelper taskHelper, ITaskItem[] winmdFiles, ITaskItem[] nonFrameworkSdkReferences, ITaskItem[] sdkWinmdFiles, String managedWinmdInprocImplementation, Boolean harvestRegistrationInformation, Boolean loadMscorlibIntoHost)
   at Microsoft.Build.AppxPackage.WinmdVisitor.Process(AppxPackagingTaskHelper taskHelper, ITaskItem[] winmdFiles, ITaskItem[] nonFrameworkSdkReferences, ITaskItem[] sdkWinmdFiles, String managedWinmdInprocImplementation, Boolean harvestRegistrationInformation)
   at Microsoft.Build.AppxPackage.GenerateAppxManifest.UpdateWinmdRegistration()
   at Microsoft.Build.AppxPackage.GenerateAppxManifest.ProcessDocument()
   at Microsoft.Build.AppxPackage.GenerateAppxManifest.ExecuteImplementation()
   at Microsoft.Build.AppxPackage.AppxPackagingTaskHelper.Execute()
   at Microsoft.Build.AppxPackage.GenerateAppxManifest.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()SDK-TestApp


1) error C4430: missing type specifier - int assumed. Note: C++ does not support default-int error C2143: syntax 2) error : missing ',' before '&'

$
0
0








I am getting those errors "C4430" and "C2143" trying to run on vs2008 the program from the folder "C\Program Files\Microsoft SDKs\Windows\programv7.1\samples\netds\wlan\wirelessHostedNetwork". Thanks in advance for help, Francis





Error xcopy building realsense sdk

$
0
0

Hi I am building the sample projects for the Intel real sense SDK 2.0 and it is giving me the following error msg

I am running MS visual studio as admin it is 2017 version 

SeverityCode DescriptionProjectFileLineSuppression State
ErrorMSB3073 The command "xcopy /y "C:\Program Files (x86)\Intel RealSense SDK 2.0\bin\x64\realsense2.dll" "C:\Program Files (x86)\Intel RealSense SDK 2.0\samples\x64\Debug\"
:VCEnd" exited with code 9009.captureC:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.CppCommon.targets138

I can't see any error code message as most people are getting like exited with error code X.

thanks for your help.

 

Unresolved External symbol_assume cs:code,Assembly Language

$
0
0

Here I list my code copied from an asm document. And then, I list my question.

1. code part

assume cs:code

code segment
mov ax,2000h
mov ds,ax
mov al,[0]
mov bl,[1]
mov cl,[2]
mov dl,[3]
mov ax,4c00h
int 21h
code ends
end

2. question part

On my Virtual computer, I saved a set of programme. they are masm.exe and link.exe. When I use them under the Win32 console, the code showed above word properly. I'll list the details of the steps here.

  1. I open Win32 console through the combination key like <win>+<R>. Then relocated the catalogue of it to the place where my asm file, masm.exe and link.exe is saved.
  2. From the console type the command "masm xxx". The OS create xxx.obj file.
  3. From the console type the command "****". The OS create xxx.exe file.
  4. From the console type the command "xxx". The OS run the xxx.exe file.

that is, the asm file is successfully compiled and run. But when I use VS 2017 to run this same code, error LNK2001 and LNK1120 are emerged on the bottom of my screen. WTF!!! I need help there!

cl.read.1.tlog files (dependency files) contains different information for different platforms

$
0
0

Hello,

the cl.read.1.tlog file contains dependency information for each .cpp file. Current I compile for the platforms Win32 and x64 with Visual Studio 2015 SP 3. The settings for both platforms are similar. The problem is: when I change a header file, the compiled source files are different. The result of the comparison of cl.read.1.tlog (Win32|x64) shows differences.Normally, I would expect both files to be the same, with exceptions of special platform specific dependencies.

Does anybody have any ideas as to how I can further diagnose or fix this problem?

Thanks.


Turn off MSBuild Warning MSB8051

$
0
0

After much effort, we have only very recently got our build warning count down to a nice 0.  However recently, Microsoft added a new one for us.

"warning MSB8051: Support for targeting Windows XP is deprecated and will not be present in future releases of Visual Studio. Please see https://go.microsoft.com/fwlink/?linkid=2023588 for more information."

How to get rid?

(we have to still support XPEmbedded until next year, when Microsoft stop supporting it, so switching toolchain is not currently an option)

visual studio does not work properly

$
0
0

I get all kinds of error messages every time I try to run something in VS.  I am using Console Application for C programming for class at UCSC Extension.   Here is some of the error msgs I get:

Error1 error : The source file for this compilation can be found at: "C:\Windows\TEMP\75c91966-1508-4f46-a6ae-a4c12f686941.txt"C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\CodeAnalysis\Microsoft.CodeAnalysis.targets2145 ConsoleApplication2

Error2 error MSB3758: An error has occurred during compilation. error CS2001: Source file 'C:\Windows\TEMP\ne3mzl0u.0.cs' could not be foundC:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\CodeAnalysis\Microsoft.CodeAnalysis.targets2145 ConsoleApplication2

Error3 error MSB3758: An error has occurred during compilation. warning CS2008: No source files specifiedC:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\CodeAnalysis\Microsoft.CodeAnalysis.targets2145 ConsoleApplication2

Error4 error MSB4036: The "SetEnvironmentVariable" task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is "public" and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with <UsingTask> in the project file, or in the *.tasks files located in the "C:\Program Files (x86)\MSBuild\12.0\bin" directory.C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\CodeAnalysis\Microsoft.CodeAnalysis.targets2145 ConsoleApplication2

5IntelliSense: expected a '{'c:\Users\Carolynn\Documents\Visual Studio 2013\Projects\ConsoleApplication2\ConsoleApplication2\Session6.c71 ConsoleApplication2

This last msg please ignore, it looks like it is saying that I do not have } when I do.  but that does not matter.  No matter what I do I can not run anything, if I say yes to compile anyway I always get this msg:

The system cannot find the path specified.  

press any key to continue . . . 

Can you tell me what is wrong,  I have tried uninstalling and downloading several different ways and end up with the same result every time.

Please respond, you can reach me at CarolynnCSF@Gmail.com  or CarolynnCSF@Yahoo.com

Thank you, Carolynn


Cre84U2 you can also reach me at CarolynnCSF@Gmail.com


Know the Visual Studio key container before the first build

$
0
0

I'm trying to automate all the build & release process in our company and I'm struggling with a very small step: the PFX key import in the local machine. For example we have a new build machine and the code we want to build is signed during the build via a PFX file that is password-protected. When I run the build in TFS on this machine the build fails with this error

Error MSB3325:Cannotimport the following key file:Mykey.pfx.The key file may be password protected.To correct this,try to import the certificate again or manually install the certificate to the StrongName CSP with the following key container name: VS_KEY_03AD4638FE10A12F

Good, I can add the PFX in the container VS_KEY_03AD4638FE10A12F using the sn.exe utility...but this is a manual step required after a first failed build occours, and I need it to fail to know the container name to use for the key import via sn.exe.

Instead, I would like to provide a build machine that is already able to compile the code.

How is that container name generated? Is there any way to tell in the source code a fixed container to use so that it does not change each time a new machine is used to build? Or, can we retrieve the key container that will be used before the build so that I add a build step that imports the PFX file? Or moreover, is there any "generic" key container I can use (that will be the same for all the machines)?

Thank you

MS Build Extensions file corrupt my bin (Web API) folder

$
0
0

For some .NET standard 1.6 reasons, MSBuild (within Visual STudio 2017 15.3.4 and 15.3.3) copies OLD dlls from this path

C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\Microsoft\Microsoft.NET.Build.Extensions\net461\lib

to my bin folder.

my Azure Project, includes the .NET 1.61 standard package as a dependency. MSBuild now INCORRECTLY overwrites the Dll's that are newer from Nuget (e.g. System.Runtime.Serialization.Xml, System.Runtime.Serialization.Xml). And this creates a DLL HELL (again? Come on Microsoft!)

My libraries are compiled using .NET 4.7.

How to fix this besides removing the .NET 1.61 standard?? (note: Many Azure library files already depend on this package)




Error in VS Build: Files has invalid value "

$
0
0

I am having the following errors in my VS build

 

Error 2 Files has invalid value "<<<<<<< .mine". Illegal characters in path.

 

The only info coming out is the Project its associated with, however there is no file with this name.  Any help would be appreciated.  It is a working copy of a subversion controlled project (client is tortoise svn).  But I can't see how this would be cause the problem with the build process?

 

Kind Regards,

Luke Cloudsdale


How to pack the products from multiple projects into one nuget without any nuspec file?

$
0
0

I am using Sdk projects targeting .NET Framework 4.7.2. The project structure is:

SmokeTests
 |
 +--UITests
 |   |
 |   +--Common
 |
 + NonUITests
     |
     +--Common

where:

  • the SmokeTests project references both UITests and NonUITests using ProjectReferences
  • UITests and NonUITests both reference Common using a ProjectReference
  • UITests, NonUITests and Common reference some NuGet packages using PackageReferences
  • the SmokeTests project has no source code, but it does have some content files.

I use the SmokeTests project as a roll up project. When I build it, its bin\debug\net472 directory contains all the binaries and symbols I want to have in the nuget package, i.e.:

  • The NuGet dependencies of UITests, NonUITests and Common
  • The dlls of UITests, NonUITests and Common
  • The PDBs

The SmokeTests csproj looks like this:

<Project Sdk="Microsoft.NET.Sdk"><PropertyGroup><TargetFramework>net472</TargetFramework><PackageId>SmokeTests</PackageId><NoPackageAnalysis>true</NoPackageAnalysis><IncludeBuildOutput>true</IncludeBuildOutput><GeneratePackageOnBuild>true</GeneratePackageOnBuild><ContentTargetFolders>content</ContentTargetFolders></PropertyGroup><ItemGroup><Content Include="**\*.ps1" Exclude="PSTests\run.ps1" /></ItemGroup><ItemGroup><ProjectReference Include="..\NonUITests\NonUITests.csproj" /><ProjectReference Include="..\UITests\UITests.csproj" /></ItemGroup></Project>


I also have a Directory.Build.props file:

<Project><PropertyGroup><TreatWarningsAsErrors>true</TreatWarningsAsErrors><AllowedReferenceRelatedFileExtensions>.pdb</AllowedReferenceRelatedFileExtensions><Version>$([System.Text.RegularExpressions.Regex]::Match($(BuildName), `\d+\.\d+(?:.\d+)?(?:.\d+)?`))</Version><Version Condition="'$(Version)' == ''">1.0.0.0</Version><SourceRevisionId>$(Revision)</SourceRevisionId><Company>My Company, Inc.</Company><Copyright>Copyright © $([System.DateTime]::Now.Year) by My Company, Inc. All rights reserved.</Copyright><Product>Smoke Tests</Product><NeutralLanguage>en-US</NeutralLanguage></PropertyGroup></Project>

When I build the solution, the produced SmokeTests.1.0.0.nupkg file does not contain any of the binaries, except the SmokeTests.dll itself. Clearly not what I want.

How can I get everything from bin\debug\net472 into the produced NuGet package **without specifying a nuspec file**? 

I can always hack an after build step that would manipulate the nupkg file, but I want a proper way to do it.

The question is also asked here - https://stackoverflow.com/questions/53625112/how-to-pack-the-products-from-multiple-projects-into-one-nuget-without-any-nuspe


How to specify Windows 10 SDK version for MSBuild.exe

$
0
0

hi,

I am using MSBuild to build a VC project, the default SDK version is selected as 10.0.14393,  How do I change the SDK version for the building?

Thanks


How to build SEAL in VS?

struct redefinition while building legacy code

$
0
0

I was trying to rebuild some legacy code, but I was getting the following error:

c:\program files (x86)\microsoft sdks\windows\v7.0a\include\wtypes.h(501) : error C2011: '_COAUTHIDENTITY' : 'struct' type redefinition
        C:\Program Files (x86)\Windows Kits\8.0\Include\shared\wtypesbase.h(260) : see declaration of '_COAUTHIDENTITY'

Does anyone know why this is happening?  I just pulled the data from our old TFS server, so it did work at one point.  I had to install VS2010 because of the older libraries.  It looks like there is something that I have to tweek?

The VC++ directories are:

Executable Directories: $(ExecutablePath);$(MSBuildProjectDirectory)\..\..\..\third_party\cygwin\bin\;$(MSBuildProjectDirectory)\..\..\..\third_party\python_26\

Include Directories: $(VCInstallDir)include;$(VCInstallDir)atlmfc\include;$(WindowsSdkDir)include;$(FrameworkSDKDir)\include;

Reference Directories: $(VCInstallDir)atlmfc\lib;$(VCInstallDir)lib

Library Directories: $(VCInstallDir)lib;$(VCInstallDir)atlmfc\lib;$(WindowsSdkDir)lib;$(FrameworkSDKDir)\lib

Source Directories: $(VCInstallDir)atlmfc\src\mfc;$(VCInstallDir)atlmfc\src\mfcm;$(VCInstallDir)atlmfc\src\atl;$(VCInstallDir)crt\src;

Exclude Directories: $(VCInstallDir)include;$(VCInstallDir)atlmfc\include;$(WindowsSdkDir)include;$(FrameworkSDKDir)\include;$(MSBuildToolsPath32);$(VCInstallDir)atlmfc\lib;$(VCInstallDir)lib;

Any help is greatly appreciated.

A


I don't mind someone marking a post as "Proposed as answer", but DO NOT mark it as "Answered". If I am the OP, I will decide if a post actually answers my post or not. Thank you.

VS2015 - Build Installer Project - keeps loosing Registry Setting

$
0
0

We upgraded projects from VS2010 to 2015, as VS2015 does not support nstaller projects we made the following changes to our build server environment

1. Installed the msi addin for Visual Studio 2015 from https://visualstudiogallery.msdn.microsoft.com/f1cc3f3e-c300-40a7-8797-c509fb8933b9

2. applied the following Registry setting

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\14.0_Config\MSBuild\EnableOutOfProcBuild (DWORD:0)

The registry setting was applied whilst logged on as a known Domain User account which is a member of the Administrators Group on the build Server, this is the same account that the TFS Build Service runs as.

Everything works fine, but at what appears to be random intervals of a week or two we get the following errors

ERROR: An error occurred while validating.  HRESULT = '8000000A'

which are an indication that the Registry setting has gone missing. 

The last time I put the registry setting back whilst logged on as myself (not the build user) and that in fact fixed the build.

We now have a very fragile automated build process which seems to break because this registry setting goes missing.

  
Viewing all 2763 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>