Hello,

I tried building my project/solution, but after the successful build, the CODED UI scripts doesn't show up in the Test Explorer.

I am shown the following error:

------ Discover test started ------
No plugin found which can import settings file with extension '.nunit'. Either select a new settings file or install an extension which understands this settings file extension.

Tried Cleaning/Rebuilding the Solution but to no avail.

Also, changed the Processor Architecture from x64 to x86 and vice - versa, still did not work out.

Could you please help me out in this regard.

Regards,

Shouvik

Our Visual Studio continuous integration builds are failing after upgrading to VS2015.  There seems to be two issues.  First, the C# new features in the V6.0 compiler do not seem to be present.  Secondly, the Azure SDK V2.8 does not seem to be present.  I believe both of these issues are configuration problems on the TFS On-Line Hosted build server but do not know what needs to be modified.

Build errors are as follows.

Paul

Please,

What is this error that comes up when I try to create an app packages? 

Here it is in its entirety:

"SeverityCodeDescriptionProjectFileLineSuppression State
ErrorValidation error. error C00CE169: App manifest validation error: The app manifest must be valid as per schema: Line 26, Column 25, Reason: Το '' παραβιάζει τον περιορισμό enumeration του 'badge badgeAndTileText'. Απέτυχε η ανάλυση του χαρακτηριστικού 'Notification' με τιμή ''.DictationC:\Users\oakba\Documents\Visual Studio 2015\Projects\Dictation\Dictation\bin\ARM\Release\AppxManifest.xml"

Aparently, the Notification attribute in the AppxManifest.xaml is invalid...

Notification=""

So I enter a value within the quotes, such as 'badge', but it does not get saved.

Can someone please explain what I need to do?

Thanks in Advance!

Hey Guys,

I was wondering if any else has seen this weird behaviour. Building with Visual Studio 2015 with "%VS140COMNTOOLS. Just using msbuild to build project in a build.bat file and I notice that some pdb's get generated and they just disapppear a few minutes later, deleted and the sometimes they wont get deleted and exist after the build is complete. Completely random when this happens.

Has anyone experience this ?

Any help much apprepicated.

Thanks,

gazmaxman

Hi,

This is my post build command:

"

i run vs2010, the command registers the dll but wont register the executable specified by $(TargetPath) even when replaced

with the full path (surrounded by quotes), also i run VS as admin,

Error message:

VCEnd" exited with code -1073741515.

Hope you can help :)

Hi,

    I am not sure if I am posting this in correct forum.So, please let me know where to post this problem. In my solution, I have 33 projects. When I build solution in Debug mode, build succeeds. When I try to build it in Release mode, Build fails. One of the common kind of error that is coming is:

Error 122 The referenced assembly "C:\Inetpub\wwwroot\PBUILDUTIL\PBuild\MDSERVE\ControlLibrary\bin\Release\MDServe.PMS.ControlLibrary.dll" was not found. If this assembly is produced by another one of your projects, please make sure to build that project before building this one. PMSUI

Error 4 Warning as Error: 'System.Configuration.ConfigurationException.ConfigurationException(string, System.Exception)' is obsolete: 'This class is obsolete, to create a new exception create a System.Configuration!System.Configuration.ConfigurationErrorsException' C:\Inetpub\wwwroot\PBUILDUTIL\PBuild\MDSERVE\

Microsoft.ApplicationBlocks.ConfigurationManagement\ConcreteFactories.cs 245 12 ConfigurationManagement

I don't get any error when I use Debug mode build.I want to build solution in release mode as in Debug mode, size of build is pretty large.

Regards

Hello,

I've a problem with one Team-Project using GIT, i', not able to build the project because tfs is not able to check out the sources:

Exception Message: TF214017: Unable to create the MSBuild project file vstfs:///Git/VersionedItem/License_Center_02/License_Center_02/develop/build/develop/TFSBuild.proj. Additional information: Git repository for path vstfs:///Git/VersionedItem/License_Center_02/License_Center_02/develop/build/develop/TFSBuild.proj was not found.. (type ProjectFileCreationException)

I triple checked the paths, google told me nothing that really helps. I tested the whole thing by moving the sources into a testproject named testprojgit, after checking in and seting up the build it was successful immedialtely. How can that be, do you have any tipps? I suggested the underscores in the name, but regarding the naming-guides they are ok when not at the start of a name.

Thanks for your help.

Im Using the Microsoft Build Tools 2015 an a build agent.

Compilation of the a VC++ project with msbuild fails because VCTargetsPath.

Registry entry seems to be correct. The path is set for tool version 4.0 and 14.0

How do i get the registry value in my environment?

Hello there,

I am trying to build zlib with visual studio 2012. I had a working vcproj from VS 2008 and just upgraded that to VS 2012. The vc90sp1 build works just fine but with vc110 I keep getting this error:

  C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB4018: The "CL" task failed unexpectedly. [Y:\src\zlib\build\obj\win64\zlib\build\projects\visualc11\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB4018: System.TypeInitializationException: The type initializer for 'Microsoft.Build.Utilities.FileTracker' threw an exception. ---> System.ArgumentException: The path is not of a legal form. [Y:\src\zlib\build\obj\win64\zlib\build\projects\visualc11\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB4018:    at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength) [Y:\src\zlib\build\obj\win64\zlib\build\projects\visualc11\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB4018:    at System.IO.Path.GetPathRoot(String path) [Y:\src\zlib\build\obj\win64\zlib\build\projects\visualc11\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB4018:    at Microsoft.Build.Utilities.FileTracker..cctor() [Y:\src\zlib\build\obj\win64\zlib\build\projects\visualc11\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB4018:    --- End of inner exception stack trace --- [Y:\src\zlib\build\obj\win64\zlib\build\projects\visualc11\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB4018:    at Microsoft.Build.CPPTasks.CL.ComputeOutOfDateSources() [Y:\src\zlib\build\obj\win64\zlib\build\projects\visualc11\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB4018:    at Microsoft.Build.CPPTasks.TrackedVCToolTask.SkipTaskExecution() [Y:\src\zlib\build\obj\win64\zlib\build\projects\visualc11\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB4018:    at Microsoft.Build.Utilities.ToolTask.Execute() [Y:\src\zlib\build\obj\win64\zlib\build\projects\visualc11\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB4018:    at Microsoft.Build.CPPTasks.TrackedVCToolTask.Execute() [Y:\src\zlib\build\obj\win64\zlib\build\projects\visualc11\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() [Y:\src\zlib\build\obj\win64\zlib\build\projects\visualc11\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppCommon.targets(347,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext() [Y:\src\zlib\build\obj\win64\zlib\build\projects\visualc11\zlib.vcxproj]

Any ideas on how to resolve this?

How we can execute the Visual Studio - Clickonce - Publish by using MSBuild script?

Do we have any powershell commands?

I heard that "ClickOnce setting manipulation and deployment is not available via scripting or MSBuild commands" is this true?, if not how we can achieve this?

Please help us.

I am having the following error when compiling Xamarin Forms PCL project after adding a Xaml Page.

<path>\MainPage.xaml.cs(15,13,15,32): error CS0103: The name 'InitializeComponent' does not exist in the current context

The same error is encountered when compiling some of their sample projects.

After searching this error in Xamarin community, people mentioned about saving the file again or changing the custom tool, nothing has helped so far really.

Can you please advise?

I have created a msi installer using Wix Bootstrap installer.When I click on the installer to install it, nothing happens. When I checked the log output I found the following issue

[2950:2990][2016-04-08T11:11:25]e000:Error0x80131902:Failed to run per-user mode.[2950:2990][2016-04-08T11:11:25]i007:Exit code:0x80131902, restarting:No

Below is my class that extends BootstrapperApplication.

public class CustomBootstrapperApplication : BootstrapperApplication
{
    public static Dispatcher Dispatcher { get; set; }
    protected override void Run()
    {
        Dispatcher = Dispatcher.CurrentDispatcher;
        var model = new BootstrapperApplicationModel(this);
        var viewModel = new InstallViewModel(model);
        var view = new InstallView(viewModel);
        model.SetWindowHandle(view);
        this.Engine.Detect();
        view.Show();
        Dispatcher.Run();
        this.Engine.Quit(model.FinalResult);
    }
}

Below is my AssemblyInfo.cs

using System.Reflection;
using System.Runtime.CompilerServices;
using System.Runtime.InteropServices;
using CustomBA;
using Microsoft.Tools.WindowsInstallerXml.Bootstrapper;

// General Information about an assembly is controlled through the following
// set of attributes. Change these attribute values to modify the information
// associated with an assembly.
[assembly: AssemblyTitle("CustomBA")]
[assembly: AssemblyDescription("")]
[assembly: AssemblyConfiguration("")]
[assembly: AssemblyCompany("")]
[assembly: AssemblyProduct("CustomBA")]
[assembly: AssemblyCopyright("Copyright ©  2016")]
[assembly: AssemblyTrademark("")]
[assembly: AssemblyCulture("")]

// Setting ComVisible to false makes the types in this assembly not visible
// to COM components.  If you need to access a type in this assembly from
// COM, set the ComVisible attribute to true on that type.
[assembly: ComVisible(false)]

// The following GUID is for the ID of the typelib if this project is exposed to COM
[assembly: Guid("0640182b-2d21-4f58-ad2a-7a4efc1d5d94")]

// Version information for an assembly consists of the following four values:
//
//      Major Version
//      Minor Version
//      Build Number
//      Revision
//
// You can specify all the values or you can default the Build and Revision Numbers
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("1.0.0.0")]
[assembly: AssemblyFileVersion("1.0.0.0")]

[assembly: BootstrapperApplication(
typeof(CustomBootstrapperApplication))]

Below is my BootstrapCore.config file

<?xml version="1.0" encoding="utf-8" ?><configuration><configSections><sectionGroup name="wix.bootstrapper" type="Microsoft.
Tools.WindowsInstallerXml.Bootstrapper.BootstrapperSectionGroup,
BootstrapperCore"><section name="host" type="Microsoft.Tools.
WindowsInstallerXml.Bootstrapper.HostSection, BootstrapperCore" /></sectionGroup></configSections><startup useLegacyV2RuntimeActivationPolicy="true"><supportedRuntime version="v4.5" /></startup><wix.bootstrapper><host assemblyName="CustomBA" /></wix.bootstrapper></configuration>

 added this project as a dependency to my Bootstrap project. Below is the bootstrap project's Product.wxs.

<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" ><Bundle Name="MyBootstrapper" Version="1.0.0.0" Manufacturer="WiX Tests" UpgradeCode="416b6bbf-2beb-4187-9f83-cdb764db2840"><BootstrapperApplicationRef Id="ManagedBootstrapperApplicationHost"><Payload SourceFile="$(var.CustomBA.TargetDir)CustomBA.dll" /><Payload SourceFile= "$(var.CustomBA.TargetDir)BootstrapperCore.config" /><Payload SourceFile= "$(var.CustomBA.TargetDir)BootstrapperCore.xml" /><Payload SourceFile= "$(var.CustomBA.TargetDir)Microsoft.Practices.Prism.Mvvm.Desktop.dll" /><Payload SourceFile= "$(var.CustomBA.TargetDir)Microsoft.Practices.Prism.Mvvm.dll" /><Payload SourceFile= "$(var.CustomBA.TargetDir)Microsoft.Practices.Prism.SharedInterfaces.dll" /></BootstrapperApplicationRef><WixVariable Id="WixMbaPrereqLicenseUrl" Value=""/><WixVariable Id="WixMbaPrereqPackageId" Value=""/><Chain><MsiPackage Id="Myapp" SourceFile="Lib\MyInstaller.msi" Compressed="yes" Vital="yes" /></Chain></Bundle></Wix>

mayooran99

Hello,

I am geeting below error while porting my existing code base from VS 2010 into VS 2015.

Error C2956 sized deallocation function 'operator delete(void*, size_t)' would be chosen as placement deallocation function.

I have searched in the internet and MS forum and try to use/Zc:sizedDealloc- but it is not helping me atall.

PLease help me in this regard.

Thanks,

Ash

Hello,

This morning I have been publishing both a debug and release build of a website that is merged into a single assembly with the "treat as a library component" enabled.

I checked the assembly information afterwards to discover that the debug publish is actually compiled in release mode, and is optimized.

Is this expected behaviour for a website publish?

Here is the pubxml for the release version:

<PropertyGroup><TargetDir Condition="'$(TargetDir)'==''">..\</TargetDir><PrecompileBeforePublish>True</PrecompileBeforePublish><EnableUpdateable>False</EnableUpdateable><DebugSymbols>False</DebugSymbols><WDPMergeOption>MergeAllOutputsToASingleAssembly</WDPMergeOption><UseMerge>True</UseMerge><SingleAssemblyName>#########</SingleAssemblyName><DeleteAppCodeCompiledFiles>True</DeleteAppCodeCompiledFiles></PropertyGroup><PropertyGroup><WebPublishMethod>FileSystem</WebPublishMethod><LastUsedBuildConfiguration>Release</LastUsedBuildConfiguration><LastUsedPlatform>Any CPU</LastUsedPlatform><SiteUrlToLaunchAfterPublish /><LaunchSiteAfterPublish>True</LaunchSiteAfterPublish><ExcludeApp_Data>True</ExcludeApp_Data><publishUrl>$(TargetDir)Publish\Release\Offline\</publishUrl><DeleteExistingFiles>True</DeleteExistingFiles></PropertyGroup>

And here is the pubxml for the debug version

<PropertyGroup><TargetDir Condition="'$(TargetDir)'==''">..\</TargetDir><PrecompileBeforePublish>True</PrecompileBeforePublish><EnableUpdateable>False</EnableUpdateable><DebugSymbols>True</DebugSymbols><WDPMergeOption>MergeAllOutputsToASingleAssembly</WDPMergeOption><UseMerge>True</UseMerge><SingleAssemblyName>#######</SingleAssemblyName><DeleteAppCodeCompiledFiles>True</DeleteAppCodeCompiledFiles></PropertyGroup><PropertyGroup><WebPublishMethod>FileSystem</WebPublishMethod><LastUsedBuildConfiguration>Debug</LastUsedBuildConfiguration><LastUsedPlatform>Any CPU</LastUsedPlatform><SiteUrlToLaunchAfterPublish /><LaunchSiteAfterPublish>True</LaunchSiteAfterPublish><ExcludeApp_Data>True</ExcludeApp_Data><publishUrl>$(TargetDir)Publish\Debug\Offline\</publishUrl><DeleteExistingFiles>True</DeleteExistingFiles></PropertyGroup>

You can see from the build output that aspnet_compiler has been told to build as debug

Task "AspNetCompiler"
Task Parameter:PhysicalPath=C:\User_Temp\WebSitePublish\############--1888659248\obj\Debug\AspnetCompileMerge\Source
Task Parameter:TargetPath=C:\User_Temp\WebSitePublish\############--1888659248\obj\Debug\AspnetCompileMerge\TempBuildDir
Task Parameter:VirtualPath=/############Task Parameter:Debug=True
Task Parameter:Updateable=False
Task Parameter:KeyFile=############.snk
Task Parameter:Clean=True
Task Parameter:ToolPath=C:\Windows\Microsoft.NET\Framework\v2.0.50727
AspNetCompiler: C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_compiler.exe -v /############ -p C:\User_Temp\WebSitePublish\############--1888659248\obj\Debug\AspnetCompileMerge\Source -c -d C:\User_Temp\WebSitePublish\############--1888659248\obj\Debug\AspnetCompileMerge\TempBuildDir -keyfile "############.snk"  

Just upgraded to Windows 10 and VS 2015.

On a basic UWP app with some nuget references the building process takes almost 1 minute. It stays mostly at "1>  Generating native code"

Then to create store packages it takes even longer, about 5 minutes.

Regards

I have property defining dependencies

<XDepends>a;b;d</XDepends>

how can i convert it to item group or somehow iterate on all the values seprted be ;

Thanks,

Sajjad

I've installed VS"15", which I use as a source of command-line tools, rather than as an IDE. Looking around, I find I have two different CSC.EXE C# compilers, in different directories and with different version numbers. 

One is in "C:\Program Files (x86)\MSBuild\15.0\Bin\csc.exe", and is "Microsoft (R) Visual C# Compiler version 2.0.0.60317" and the other is in "C:\Windows\Microsoft.NET\Framework[64]\v4.0.30319\csc.exe" and is "Microsoft (R) Visual C# Compiler version 4.6.1055.0"

What's the difference? Why are there two? 

NB: I do not use MSBuild for anything, because I don't use Visual Studio Projects for anything, at all. I'm strictly a command-line worker, because I work with a programming language that the Visual Studio IDE doesn't understand, which gets compiled into C. I use C# to provide a .NET wrapper for the code I build from this C, but my C# code is not written by hand, but generated by a Perl script, which basically creates a lot of P/Invoke calls. So I'm not especially concerned about access to new language features, but I am concerned about the .NET DLL I produce from this generated code being usable with both C# compilers, if it makes a difference. I have used the one from C:\Windows\Microsoft.NET\Framework[64]\" historically, and if there's no reason to change, I'll carry on doing so. 

John Dallman

For an NMAKE guru this is probably and elementary question.

I'm building open-source GEOTIFF libraries; however, to do so one must first edit the Makefile.vc and set  the BUILD (absolute) PATHS to TIFF and  PROJ4 directories at the start of the Makefile.vc residing in the libgeotiff repository.  This is not really acceptable since the path includes specific project folders/directories to your current build area. I'd like to make this more adaptable for any project.  Is there way to pass in paths in the NAMKE process, say as arguments? 

Currently I nmake from the VS command line - Visual Studio Tools >> Visual Studio Command Prompt. This all works fine just a-bit clunky.

I see I can create an  MAKEFILE visual studio project. Anyone aware of examples replacing the command namke  /f Makefile.vc process to the VS2010 Makefile project.   

I use the nmake process to build static libraries from the open-source which I use to link to with a VB.NET(Managed)/CLI/C(Unmanaged) project

At a high level of abstraction....

I nmake PROJ4 to get a proj.lib library

I nmake TIFF to get a libtiff.lib library

Finally, I nmake LIBGEOTIFF to create geotiff.lib library which requires the latter two libraries above.

So, If I were to create VS Makefile Projects would I create 3 separate Makefile projects?

I have also tried to create a VS "Class Library" Project with some moderate success but but there were some other issues with function name resolution going between C++ and C. It seem best to stick with the suggested LIBGEOTIFF/TIFF linking process.

I' suppose I'm looking for a other strategies.  Maybe the use of the VS 2010 Command line compilation is the best methodology. I have actually developed all the VB/CLI interfaces with my static (unmanaged) libraries and everything works fine. I just wanted to see if I could improve the library build processes on the open-source stuff.