[I'm using versions 2017 of both Unity and Visual Studio, but I don't think that bears on this problem because the same issue existed in Visual Studio 2015 and Unity 5.5]
I have created a Build Configuration (Staging) via VisualStudio/Build/Configuration Manager/Active Solution Configurations/[new]
I have then created a publish profile for my WCF Service Application that pairs the Staging build configuration to a Web.Staging.config transform file.
The problem is that whenever Unity syncs up the solution file it removes this build configuration which breaks this publish profile and results in the Web.Debug.config transformation being used rather than Web.Staging.config.
So, my question is, how do I get Unity to leave this build configuration in the .sln file?
Related
I am trying to develop my own plugins in xamarin form. I installed Cross-Platform .NET Standard Plugin Templates in VS 2019. I can see in description Cross-Platform .NET Standard Plugin Templates works with 2017 and 2019.
When I try to create new project it keeps going on saying creating project.
When I look in the directory, I can see some files being generated.
It's an existing issue with VS2019
Creating a new Project with VS2019 shows missing references / they cant be loaded. Appeared after last VS Update.
If you wait long enough you can do the following :
Note- after last VS 2019 update- edit the csproj file and update the MSBuild.Sdk.Extras to version 2.0.54 so all dependencies load and the project will build.
UPDATE:
Had to download Visual studio 2017 to create the project
I have some merge module projects created using advanced installer. I need to integrate them with visual studio. I have done same for MSI projects and they work fine. but I don't know how to achieve continuous integration for MSM using Visual Studio.
Advanced Installer extension for Microsoft Visual Studio allows to create Advanced Installer Projects for Visual Studio. Each such project is a container that can include a single .AIP file.
The Visual Studio Solution can include one or more Advanced Installer Project for Visual Studio, in accordance with your needs.
Note that you need to remove the default project that is created when adding a new Installer Project to the .sln and add the existing project, the project that builds the .msm package.
edit
Indeed, you are right. It was a misunderstanding on our end.
On my machine I have several extensions installed side by side. One of these extensions also supports the build of a merge module project type.
We do not officially support this yet. The option to build other project types (e.g. Merge Module Project, Updates Configuration Project) with our VS extension will be available in a future version of Advanced Installer. I will let you know when we will add support for this.
Until then, you can use a build event as a workaround to build the Merge Module Project within the Visual Studio project.
To build the .msm project you can use a command line as described below:
http://www.advancedinstaller.com/user-guide/command-line.html#build-project
The command line can be something as below:
AdvancedInstaller.com" /build "$(SolutionDir)Merge module sample.aip"
I am working with Microsoft Visual Studio and have a problem when opening a solution file. The solution file consists of a core project and multiple plugin projects. During development, there may be instances where every plugin project is not extracted with the core.
When opening this solution file during development, Visual Studio will complain about missing plugin projects and will have a separate pop-up window for each missing project. Is there some setting in Visual Studio to turn off this warning? Ideally, I do not want to have multiple instances of the solution file or create a script to modify the solution file every time a new project is extracted from our repository. I looked through all of the settings and could not find a flag or warning to turn off.
You might have build the project in the previous version (i.e 2008) and trying to open in the newer version (i.e 2010).
Main Goal - To deploy a live version of my solution on an IIS. I am currently attempting to do so by building a deployment package through Visual Studio 2010.
Issue - When attempting to build a deployment package or publish my project within Visual Studio 2010, I get an error stating that 'bin/EntityFramework.xml' is missing.
I've done quite a bit of research and have not been able to find any information on how this file could have gone missing or how to restore/regenerate the file.
Questions - Is there any way to restore or regenerate the 'bin/EntityFramework.xml' file? Or, is there a simpler approach for deploying my VS 2010 solution to an IIS?
(FYI, I've already attempted copying the file structure to an IIS manually. This caused assembly issues, which is why I'm currently avoiding that approach.)
Thanks!
To answer the specific question first, you can easily regenerate this file by creating a new project of the same type (e.g. ASP.NET MVC3), then building that new project. EntityFramework.xml will appear in the new project's bin folder. You may then copy it over to your existing project.
However, you can just 'Exclude from Project' the missing file (via right-click in Solution Explorer), since it is not required to build, then you will achieve your goal of publishing the project through VS2010.
I'm facing quite a problem while setting up automated TFS Builds. Basically I created new configuration called Tests, added transform config, defined different connection strings for the Database. Then defined TFS build, building whole solution with MSBuild arguments /p:DeployOnBuild=True /p:Configuration=Tests.
The problem is that in the drop location (Build_PublishedWebsites\Project) I get web.config, web.debug.config, web.release.config and web.tests.config, however I would expect just one transformed web.config.
I already checked PDC presentation Web Deployment Painkillers: Microsoft Visual Studio 2010 & MS Deploy but didn't help.
Thanks for any answer.
Web.config transforms are part of the new Web Publishing Pipeline (WPP) in Visual Studio 2010.
During the build process the "CopyWebApplication" target is executed to copy the website to the _Websites folder on the build output directory. Due to backwards compatibility reasons, MSBuild uses the "old" (VS2008) copy behavior by default and not the new WPP system.
To opt-in to using WPP, set the following MSBuild properties:
/p:UseWPP_CopyWebApplication=True
/p:PipelineDependsOnBuild=False