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

error MSB3191

$
0
0

Hi everybody!

I've been trying to compile a project I have but I keep on receiving "error MSB3191 Unable to create directory "D:\MC55\release". Could not find a part of the path 'D:\MC55\release". I do not have a D drive nor do I know where this error is coming from.

I checked the project properties as well as the code itself and nowhere is it specified to look for the D Drive. I also checked the Macros in the project properties and found nothing similar to that.

This project had been compiled in the past using VS 6 but now I'm using VS 2013.

The error points to this : "<MakeDir Directories="@(LinkDirsToMake)" /> " which is situated in the file Microsoft.CPP.Build.Targets.

I tried changing some things in the code and properties but nothing worked. Anybody have any ideas why this is happening?

If any other information is needed from me just let me know!

Thanks a lot! :-)


Visual studio CL.read.1.tlog dependencies incorrect if a header incorrectly marked as "C/C++ compiler"

$
0
0

Hi,

For quite some time now we've had incremental build problems in our VS2010 project, where changes to a header were not causing items including that header to recompile (visual studio was not calculating dependencies correctly). Since we were upgrading to VS2013 soon, I thought maybe the problem would have been fixed, only to discover the problem was still there in VS2013. At the most basic level, I could do a rebuild all, then delete the contents of one header entirely, do an incremental build, and only one of perhaps six .cpp files including that header, would actually detect the header change and attempt to compile.

Looking at C1.read.1.tlog, many of the cpp files were missing .h dependencies that should be there, after a rebuild. To confuse matters, after a rebuild, if I then force compile of an individual .cpp , the C1.read.1.tlog will now show the correct set of dependencies for that file. So it only affected some files, and only when doing a project build (not when forcing an individual .cpp to compile).

I finally noticed in my .tlog there was a header file with a ^ prefix. I realized this header had been configured incorrectly, to have "Item Type" set to "C/C++ compiler", instead of "C/C++ header". Strangely, that header contained no other headers, only a simple one line forward declaration. Yet the dependencies listed for that header in the .tlog, were quite extensive, which made no sense at all.

Changing this header file to "C/C++ header" fixed the dependency problem. The C1.read.1.tlog, after a rebuild all, went from about 13MB in size, to around 42MB (reflecting all the missing dependencies that were now present).

I'm posting this as a discussion to make this information public to other users possibly experiencing this problem. It was a real headache to track down, and collectively wasted countless days, perhaps weeks of dev time, due to heisenbugs and mystery linker errors resulting from it.

To reproduce the issue, create a new visual studio project dummy project (with say Sample.cpp), add in some empty header files

"SomeHeaderFile.h"

"DependencyBreaker.h"

Then add the following to Sample.cpp

#include "DependencyBreaker.h"
#include "SomeHeaderFile.h"

Mark "DependencyBreaker.h" as "C/C+ compiler". Rebuild the project. Open C1.read.1.tlog.

Note the file content has DependencyBreaker.h listed as having a dependency, even though it doesn't include anything.

^..\CONSOLEAPPLICATION1\DEPENDENCYBREAKER.H
..\CONSOLEAPPLICATION1\CONSOLEAPPLICATION1\SOMEHEADERFILE.H

Note that Sample.cpp does not have any dependency information for the included headers. If you then force compile of Sample.cpp file in isolation, the correct dependency information will now appear in the .tlog.

If you reverse the order Sample.cpp as follows, the dependency information will correctly show "SomeHeaderFile.h", but not "DependencyBreaker.h". Additionally "DependencyBreaker.h" will have no dependencies (as expected).

#include "SomeHeaderFile.h"
#include "DependencyBreaker.h"

If you mark the DependencyBreaker.h as "C/C++ header", then the .tlog always shows the correct dependency information, regardless of rebuild all, or individually compiling the file.

Anyway I hope this information will be of use to anyone else who might have run into this issue.


C4430 error

$
0
0

Hello smart people!

I have a project that I would like to compile using VS 2013. It had been previously built on VS 6 a few years ago and everything was fine.

As I said I'm trying to compile it using VS 2013 but I am getting the following error "error C4430: missing type specifier - int assumed. Note: C++ does not support default-int"

This error appears 27 times on the error list and it points to the same line :

public:
// #pragma warning (disable : 4430);
     CSocketsFramework();

    SetSocketsParameters (CString strSMARTIPAddress, UINT iSMARTPort, long luTimeout);  ----> C4430 error is here
    virtual ~CSocketsFramework();
    //Connections methods
    BOOL ConnectToServer();    
    CString GetSocketID();

etc,

I've been reading the other threads about this particular error and even though I understand more or less the reason for it no answers have really helped me for this case.

As seen in the code I have placed "#pragma warning (disable : 4430);" which in fact makes the error message go away but when I execute the application that is created it crashes. I'm not sure but maybe it crashes due to this.

If anybody has any ideas on how to resolve this error without using the #pragma I would be very thankful!

If any more information is needed from my side please let me know!!

Thanks :-)

Building my solution takes a "long time" today

$
0
0

Hello,

Since this morning my solution is taking way more time to build. I probably made a mistake somewhere to make it happen but I can't find this problem.

So, the building time was about 1s yesterday and today it's about 12s, here is the detailed build time:

1>Target Performance Summary:
1>        0 ms  _CheckForInvalidConfigurationAndPlatform   1 calls
1>        0 ms  ImplicitlyExpandDesignTimeFacades          1 calls
1>        0 ms  CreateCustomManifestResourceNames          1 calls
1>        0 ms  GetReferenceAssemblyPaths                  1 calls
1>        0 ms  AfterCompileWinFX                          1 calls
1>        0 ms  _CopyFilesMarkedCopyLocal                  1 calls
1>        0 ms  DesignTimeMarkupCompilation                1 calls
1>        0 ms  AfterResGen                                1 calls
1>        0 ms  FileClassification                         1 calls
1>        0 ms  _CheckForCompileOutputs                    1 calls
1>        0 ms  CoreBuild                                  1 calls
1>        0 ms  ResolveReferences                          1 calls
1>        0 ms  AfterMarkupCompilePass1                    1 calls
1>        0 ms  CreateSatelliteAssemblies                  1 calls
1>        0 ms  _CopySourceItemsToOutputDirectory          1 calls
1>        0 ms  CreateManifestResourceNames                1 calls
1>        0 ms  BeforeResGen                               1 calls
1>        0 ms  DeleteBuildInfoFile                        1 calls
1>        0 ms  SetWin32ManifestProperties                 1 calls
1>        0 ms  DeleteBuildInfoResource                    1 calls
1>        0 ms  PrepareResources                           1 calls
1>        0 ms  _GenerateSatelliteAssemblyInputs           1 calls
1>        0 ms  AfterBuild                                 1 calls
1>        0 ms  AfterCompile                               1 calls
1>        0 ms  ValidationExtension                        1 calls
1>        0 ms  ComputeIntermediateSatelliteAssemblies     1 calls
1>        0 ms  CleanXsdCodeGen                            1 calls
1>        0 ms  _CleanGetCurrentAndPriorFileWrites         1 calls
1>        0 ms  GetFrameworkPaths                          1 calls
1>        0 ms  _AfterCompileWinFXInternal                 1 calls
1>        0 ms  GetCopyToOutputDirectoryXamlAppDefs        1 calls
1>        0 ms  CoreResGen                                 1 calls
1>        0 ms  Compile                                    1 calls
1>        0 ms  _SetEmbeddedWin32ManifestProperties        1 calls
1>        0 ms  AssignTargetPaths                          1 calls
1>        0 ms  BeforeBuild                                1 calls
1>        0 ms  ExpressionBuildExtension                   1 calls
1>        0 ms  ResolveProjectReferences                   1 calls
1>        0 ms  PreXsdCodeGen                              1 calls
1>        0 ms  _SetTargetFrameworkMonikerAttribute        1 calls
1>        0 ms  ResolveSDKReferences                       1 calls
1>        0 ms  DesignTimeXamlMarkupCompilation            1 calls
1>        0 ms  ResGen                                     1 calls
1>        0 ms  BuildOnlySettings                          1 calls
1>        0 ms  ExpandSDKReferences                        1 calls
1>        0 ms  GenerateCompiledExpressionsTempFile        1 calls
1>        0 ms  PrepareForRun                              1 calls
1>        0 ms  GetCopyToOutputDirectoryItems              1 calls
1>        0 ms  BeforeCompile                              1 calls
1>        0 ms  CompileRdlFiles                            1 calls
1>        0 ms  AfterResolveReferences                     1 calls
1>        0 ms  PrepareForBuild                            1 calls
1>        0 ms  Build                                      1 calls
1>        0 ms  PrepareRdlFiles                            1 calls
1>        0 ms  _CopyAppConfigFile                         1 calls
1>        0 ms  IncrementalClean                           1 calls
1>        0 ms  GetInstalledSDKLocations                   1 calls
1>        0 ms  BeforeResolveReferences                    1 calls
1>        0 ms  AssignProjectConfiguration                 1 calls
1>        0 ms  _SplitProjectReferencesByFileExistence     1 calls
1>        0 ms  GenerateTargetFrameworkMonikerAttribute    1 calls
1>        0 ms  SplitResourcesByCulture                    1 calls
1>        0 ms  PrepareResourceNames                       1 calls
1>        0 ms  _GenerateCompileInputs                     1 calls
1>        0 ms  GetTargetPath                              1 calls
1>       16 ms  SetBuildInfoDefaults                       1 calls
1>       16 ms  ResolveAssemblyReferences                  1 calls
1>       47 ms  CopyFilesToOutputDirectory                 1 calls
1>    11259 ms  CoreCompile                                1 calls
1>
1>Task Performance Summary:
1>        0 ms  GetReferenceAssemblyPaths                  1 calls
1>        0 ms  CreateCSharpManifestResourceName           1 calls
1>        0 ms  RemoveDuplicates                           2 calls
1>        0 ms  GetFrameworkPath                           1 calls
1>        0 ms  GenerateResource                           1 calls
1>        0 ms  AssignTargetPath                           6 calls
1>        0 ms  ReadLinesFromFile                          1 calls
1>        0 ms  AssignProjectConfiguration                 1 calls
1>        0 ms  CallTarget                                 1 calls
1>        0 ms  MakeDir                                    1 calls
1>        0 ms  FindUnderPath                              5 calls
1>        0 ms  Delete                                     2 calls
1>        0 ms  ConvertToAbsolutePath                      1 calls
1>        0 ms  FindAppConfigFile                          1 calls
1>        0 ms  AssignCulture                              1 calls
1>       16 ms  Message                                    3 calls
1>       16 ms  ResolveAssemblyReference                   1 calls
1>       31 ms  Copy                                       3 calls
1>    11259 ms  Csc                                        1 calls
1>
1>Build succeeded.
1>
1>Time Elapsed 00:00:11.33
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

So the problem comes from Csc and CoreCompile apparently, but I've no clue what are those and how to fix it.

System: Windows 7 entreprise SP1 64 bits

Visual studio ultimate 2013 (up to date) - trial licence

Thank you for your help.

NB: I could copy/paste the whole log but it's thousand lines long.

NB: I'm using 1.8mo lib (reference) in this solution




How to force an assembly reference to be found/used at a specific location

$
0
0

I am using VS.NET 2005 to build a C# .NET 2.0 DLL. I have a reference in the .csproj file that looks like:

 

   <Reference Include="Something">

     <Name>Something</Name>

     <HintPath>..\staging\comp\something\lib\Something.dll</HintPath>

     <Private>False</Private>

   </Reference>

 

My question is simple - I don’t ever want the build process to use this reference from the GAC, how do I prevent that? Further, I would like that if that file is not found at that exact location, that the build fail. Can that be done?

 

Thanks for any help!

Compilation problem

$
0
0

Hi,
I've got a problem with  the compilation on VS 2012. I cannot access (put a breakpoint) a file.h when my application is launched => "A copy of FILE.h was found in c:\.....\FILE.h, but the current source code is different from the version built into c:\....\FILE.h"

This problem can be solved with a rebuild.

Then, if I make a modification again on this file, the error message appears but I would like to avoid to rebuild the project each time.

Do you have any solution to solve this problem?

Thanks,

Alexandre Marcenac

Compilation problem

$
0
0

Hi,
I've got a problem with  the compilation on VS 2012. I cannot access (put a breakpoint) a file.h when my application is launched => "A copy of FILE.h was found in c:\.....\FILE.h, but the current source code is different from the version built into c:\....\FILE.h"

This problem can be solved with a rebuild.

Then, if I make a modification again on this file, the error message appears but I would like to avoid to rebuild the project each time.

Do you have any solution to solve this problem?

Thanks,

Alexandre Marcenac

VS2010 dependencies problems

$
0
0

We have recently  switched our solution from vs2008 to vs2010 and we are sometimes having dependencies problems when compiling our win32 targets. Basically, sometimes, our pch file do not get recompiled when a .h file included in it has changed. Then some cpp files that changed get recompiled but they issue errors because they are still using an old pch. This prevents our build system from working properly.

 

I was able to isolate the cause. Our pch cpp files are sometimes listed in the dependency file cl.read.1.tlog in a wrong way. Three things can happen whenever we rebuild a project. The first 2 are OK, the third is our problem.

 

1)     Sometimes, the pch.cpp file does not have an entry in the file cl.read.1.tlog. So when we compile again later, the compiler tells us that the pch is not listed in the cache and it checks the dependencies in some other way. That will be ok and the pch will be recompiled only if some of its dependencies have changed.

2)     Sometimes, the pch.cpp file is listed in cl.read.1.tlog and all its dependencies are listed with it. This is, I guess, the normal behaviour and works fine when we compile again later and some .h files have changed.

3)     Sometimes, the pch.cpp will get an entry in cl.read.1.tlog, but its list of dependencies is incomplete! It only lists the first 4 files (dll files from the windows directory) and no .h files are listed. Then when we compile again, after a sync from perforce for example, the compiler finds the pch.cpp in the cl.read.1.tlog, and uses its dependencies listed to decide if it needs recompiling. Since this dependency list is incomplete, the compiler does not see that some .h files have changed and so does not recompile the pch.cpp. Then other cpp files try to compile with an old pch file and can have build errors.

 

The third behaviour is of course the one causing us problems.

 

Here is an sample of cl.read.1.tlog for behaviour 2:

 

^F:\FC3\MAIN\CODE\CORE\CORE_PCH.CPP

C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 10.0\VC\BIN\1033\CLUI.DLL

C:\WINDOWS\GLOBALIZATION\SORTING\SORTDEFAULT.NLS

C:\WINDOWS\SYSTEM32\RSAENH.DLL

C:\WINDOWS\SYSTEM32\TZRES.DLL

F:\FC3\MAIN\CODE\CORE\COREBASIC.H

F:\FC3\MAIN\CODE\CORE\COREBASICCOMMON.H

F:\FC3\MAIN\CODE\CORE\BASIC\BASICTYPES.H

C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 10.0\VC\INCLUDE\EXCEPTION

C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 10.0\VC\INCLUDE\XSTDDEF

C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 10.0\VC\INCLUDE\YVALS.H

C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 10.0\VC\INCLUDE\CRTDEFS.H

Etc...

 

Here is an sample of cl.read.1.tlog for problematic behaviour 3:

 

^F:\FC3\MAIN\CODE\CORE\CORE_PCH.CPP

C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 10.0\VC\BIN\1033\CLUI.DLL

C:\WINDOWS\GLOBALIZATION\SORTING\SORTDEFAULT.NLS

C:\WINDOWS\SYSTEM32\RSAENH.DLL

C:\WINDOWS\SYSTEM32\TZRES.DLL

^F:\FC3\MAIN\CODE\CORE\CONTAINERS\VECTOR.CPP

F:\FC3\MAIN\TMP\WIN32\RELEASE_DLL\CORE\CORE_PCH.H.PCH

F:\FC3\MAIN\CODE\PLATFORMS\WIN32\CORE\MEM\MEMMNGBUCKETSPLATFORM.H

F:\FC3\MAIN\CODE\CORE\MEM\MEMMNGPRIVATE.H

F:\FC3\MAIN\CODE\CORE\THREAD\CRITSECTION.H

F:\FC3\MAIN\CODE\CORE\MEM\CONTEXTLOG.H

F:\FC3\MAIN\CODE\PLATFORMS\WIN32\CORE\MEM\MEMMNGCONFIG.H

Etc…

 

Notice that CORE_PCH.CPP is present in the file, but its list is incomplete.

 

Any fix for this kind of problems?

 

To temporarily bypass this problem, we have added a pre-build step on our buildmachiens that deletes all the files cl.read.1.tlog. This as fixed the problem.

 

Finally, note that we also have similar problems where we recompile some projects when they are actually already fully build. This does not break the builds, but makes our work longer because we recompile more often then needed. These problems are not happening all the time and not on all PCs. We have had this same problem by making a new simple win32 projet and chaging some .h files outside of Visual Studio. Same thing happens, only more rarely.

 

Thanks,

 

David Chabot

Ubisoft

Senior Game Engine Programmer

 

P.S. Our PCs are running Windows 7 64 bits with Visual Studio 2010 with SP1


Fx Shader effect compilation in VS 2012 Ultimate with Microsoft DirectX SDK (June 2010)

$
0
0

Hi Guys, good morning. I really need your help for compiling shader effect file .fx in VS2012.

I'm using VS 2012 Ultimate and also i installed "Microsoft DirectX SDK (June 2010)", this is the dir in my system: 

C:\Program Files\Microsoft DirectX SDK (June 2010)\Utilities\bin\x86

The fx file name is 'bricon.fx" and the output file is 'bricon.ps' and I have added this parameter in the pre-build event:

fxc /T ps_2_0 /E main /Fo”$(ProjectDir)bricon.fx” “$(ProjectDir)bricon.ps”

When i complied by clicking on "ReBuild"; i got this error message:

Please help me with  this configuration. Thank you very much.

This is the code in the file and i want to apply Brightness, Contrast, Red, Green & Blue color over the image by Sliders.

float Brightness : register(C0);
float Contrast : register(C1);
float Red: register(C2);
float Green: register(C3);
float Blue: register(C4);

sampler2D Texture1Sampler : register(S0);

float4 main(float2 uv : TEXCOORD) : COLOR
{

	float4 pixelColor = tex2D(Texture1Sampler, uv);
	pixelColor.rgb /= pixelColor.a;

	// Apply contrast.
	pixelColor.rgb = ((pixelColor.rgb - 0.5f) * max(Contrast, 0)) + 0.5f;

	// Apply brightness.
	pixelColor.rgb += Brightness;


	// Return final pixel color.
	pixelColor.rgb *= pixelColor.a;
 
	pixelColor.r += Red;
	pixelColor.g += Green;
	pixelColor.b += Blue;

//return float4(Red, Green Blue, 1);
	return pixelColor;
}

AxImp having trouble with ActiveX Control OCX

$
0
0

I'm trying to use AxImp to create a wrapper for a custom OCX that was written in C. When I try to use AxImp, it fails with the message: error CS0102: The type 'AxQNIXOCXLib.AxQnixocx' already contains a definition for 'KeyPressEvent'

If I look at the .cs file generated by AxImp, there's a KeyPressEvent function, but also a KeyPressEventEvent that gets generated for some reason. Is there something I should be looking at in the source of the original OCX perhaps?

Or given that I can get the original C source for the OCX, is there a better way of going about moving this into a .NET environment?

A C# MSBuild logger to support multiple versions of MSBuild

$
0
0

Not sure if this is a C# question or an MSBuild question.  I am a relative novice on C# and MSBuild but I developed a MSBuild logger when VS2012 came out.  Now I would like to use the same DLL for VS2013 but I get the error:

"Please verify the logger assembly has been built using the same version of the Microsoft.Build.Framework assembly as the one installed on your computer and that your host application is not missing a binding redirect for Microsoft.Build.Framework. Unable to cast object of type 'LdxLogger.MyLdxLogger' to type 'Microsoft.Build.Framework.ILogger'." 

From what i have read this is likely due to logger being built for .NET 4.0 but trying to run with the newer MSBuild.  Is there a way to make it so that the same logger DLL can be used for both environment?


Don Burn Windows Filesystem and Driver Consulting Website: http://www.windrvr.com Blog: http://msmvps.com/blogs/WinDrvr

Problems with VSHOST.EXE

$
0
0
Hi all,

I've started getting errors when building an application.  It stop building with an "This operation could not be completed" error.  If I try again, it then says "Visual Studio could not copy a support file to this location <path to VSHOST.EXE>".

I can fix the error by renaming VSHOST.EXE to VSHOST.EXE.OLD and rebuilding. 

The project is on a network share so perhaps this could be the problem

Deployment Package - Amending File Name

$
0
0

Hi

I am looking to use the deployment package functionality of MSBuild to allow automated deployment of applications to a test environment.  The standard tools are working well but I need to make a couple of amendments to fit in with the current deployment infrastructure my company uses.

The issue I am encountering is that the package uses the same file name for each build.  So for each build the zip file is called "<project>.zip" with no other unique identification associated with it.  What I would like to do is assign the build number to the file name so the finished zip file is like "<project>-1.12.23.224.zip".

I have added a *.wpp.targets file to the project and can write a target that gets the build number.  However when I try to redefine the $(PackageFileName) property of MSBuild it makes no difference.

Has anyone done anything similar or knows how to correctly redefine the name of the package that MSBuild produces.

Thanks

Colin

 

Post build events: return codes

$
0
0

Hi all

I have an custom console application (.NET 3.5) and this application is used as part of build process in post-build event command line. The application return -1 if error occurred.

What I expecting is if console app return -1 the build process in Visual Studio must terminated with Error state. But in VS2013 the build process continue even if app return -1.

My post-build event is very simple:

"..\..\Tools\MPBMaker.exe" "Test" "$(TargetDir)test.file"
echo Exit Code is %errorlevel% 

and here is result:

1>  		The process cannot access the file 'd:\My Documents\Visual Studio 2013\Projects\Test\Test\bin\Debug\Test.file' because it is being used by another process.
1>  Exit Code is -1
What am I doing wrong?


SCSMSolutions
email: freemanru (at) gmail (dot) com

file not found in obj folder after building

$
0
0

Hai

After Building the project I find nothing in obj folder as I want compiled files in obj folder after building.

I am using Crypto Obfuscator which searches obj folder for exe file for building the setup project.

thanks.


programmer


MS build arguments to compare the build output to the target database ex. TORDBD35

$
0
0

Hello there, i'm using TFS 2010 and VS 2012. I need an MS build argument to compare build server output to compare with target database ex. TORDBD35 but needs to be done without deploying it. I've to use this build definition for regression testing environment. Just created the build definition, but MS build argument line is empty. I'm confused what to fill in it for comparing to target database without need to deploy it in automated build. Please help me out with relevant MS build argument and any deployment script if it is generated through it.

Thanks

T.Uday

MSBuild on network share fails

$
0
0

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



How to correct CheckRemoteFx45 and UsingTask declaration?

$
0
0

Hi, I'm hoping someone can help me interpret this error:

Error 1 The "CheckRemoteFx45" task could not be loaded from the assembly C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.Tasks.dll.  Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.  0 0 forms

I received it when I tried to publish a simple web forms application to the azure website, from the Visual Studio 2013 Virtual Machine. The application runs on local host, and I downloaded publishing settings from the azure website. I'm unfamiliar with the UsingTask declaration, so I'd like help to locate and correct this declaration.

Why does MSBuild look for "v110" directory for the "Microsoft.Cpp.Default.props" file with VS2013?

$
0
0

Hi,

I have a VC++ project that builds successfully both with VS2010 SP1 and with MSBuild. I installed the VS2013 into the same machine and opened the project with it. VS2013 converted the project from VS2010 to VS2013. The project built successfully with VS2013. However, when I ran MSBuild, it output the following error message - "error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.Cpp.Default.props" was not found."

I verified that there was no such directory with "V110" on my computer. Instead, my machine has "V120" directory in which the specified file exists. The vcxproj file does have "<PlatformToolset>v120</PlatformToolset>" for both Debug and Release conditions. Note that I completely skipped installing VS2012.

Question: How can I let the MSBuild look for the "V120" directory?


tetsu


How to Simplify MSBuild copy files task?

$
0
0

I created a MSBuild script to copy specific files from source to destination like given below. Here in the ItemGroup for each item the source directory has to be specified ("E:\Test100\") which is repeated multiple times and hectic to specify for 100 files even if I refer it from a property (I can put it in a property, but still the property will be repeated).

Is there a way to simplify this to refer to these files from the specific directory which is defined once? The files and MSBuild script are in different locations.

Thanks in advance...

<?xml version="1.0" encoding="utf-8"?><ProjectToolsVersion="4.0"xmlns="http://schemas.microsoft.com/developer/msbuild/2003"><TargetName="CopyAllFiles"><ItemGroupLabel="FilesToCopy"><FileInclude="E:\Test100\1.txt"/><FileInclude="E:\Test100\2.txt"/><FileInclude="E:\Test100\3.txt"/><FileInclude="E:\Test100\4.txt"/><FileInclude="E:\Test100\5.txt"/><FileInclude="E:\Test100\6.txt"/><FileInclude="E:\Test100\7.txt"/><FileInclude="E:\Test100\8.txt"/></ItemGroup><CopySourceFiles="@(File)"DestinationFolder="E:\TestCopyFiles\"Retries="10"RetryDelayMilliseconds="100"></Copy></Target></Project>


Something Like this

<?xml version="1.0" encoding="utf-8"?><ProjectToolsVersion="4.0"xmlns="http://schemas.microsoft.com/developer/msbuild/2003"><TargetName="CopyAllFiles">

<PropertyGroup>

<SourceDir>E:\Test100\</SourceDir>

</PropertyGroup>
<ItemGroupLabel="FilesToCopy"><FileInclude="1.txt"/><FileInclude="2.txt"/><FileInclude="3.txt"/><FileInclude="4.txt"/><FileInclude="5.txt"/><FileInclude="6.txt"/><FileInclude="7.txt"/><FileInclude="8.txt"/></ItemGroup><CopySourceFiles="$(SourceDir)@(File)"DestinationFolder="E:\TestCopyFiles\"Retries="10"RetryDelayMilliseconds="100"></Copy></Target></Project>


Viewing all 2763 articles
Browse latest View live


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