We have a legacy C# and C++ solution (web services, web app, OWIN and Nancy) that was built with Visual Studio 2013. We now must use Visual Studio 2019 Enterprise. The solution has a .nuproj file that we were using with the open source nuproj github repo that has been archived and is unsupported in VS 2019. The nuproj authors have not supplied any help (from what I can see) on how to convert or migrate nuproj to a VS 2019 format.
I am wondering if anyone knows the quickest way to get this working?
Alternatives would also be appreciated.
I read:
Quickstart: Create and publish a NuGet package using Visual Studio (.NET Standard, Windows only), but I was hoping not to install .NET Core on my company laptop yet.
Automating creating NuGet package as part of build process, but I see that is eight years old.
Internet searches about csproj self-pack and dotnet pack, but again, I do not want .NET Core right now.
Nothing straightforward. I will retool and use NAnt.
Related
Background:
I have an MVC application recently ported to Visual Studio 2015 Pro
All relevant references are set to Copy Local = True
We are using Visual Studio Team Services (previously Visual Studio Online) for our repository
I am able to compile, publish, and run the application locally without issues
All dlls contained in the \packages folder are not getting committed to Team Services and NuGet isn't fixing this on the other machines.
How do I fix this so everyone else can compile this application?
I have read many "solutions" to this problem, but none have worked. One that seems to fix the issue for many people doesn't work in VS2015 because Microsoft removed the option to automatically restore NuGet packages.
I have searched many other sites, and similar posts on Stack, but none are exactly this issue.
Please help me fix it.
I have an old vb6 project and I want to convert vb6 project code to vb.net in Visual Studio 2008. By using upgrade wizard in vs2008 I opened .vbp(Old vb6) file.
It is successfully opened, but I got an error. Please give me the appropriate solution for this.
upgrade failed when I tried to convert vb6 project to vb.net using upgrade
wizard in visual studio 2008. Plz solve this issue.Thanks in advance.
It looks to me that the libraries referenced by your VB6 project are not installed and registered on your Visual Studio 2008 machine.
Does this project run in VB6 on the same machine? If not, you will need to copy all of the missing OCX files to your VS2008 machine and use regsvr32.exe to register each one individually before attempting your conversion.
We have SQL CLR dll that we developed quite a long time ago that we have been using. Unfortunately it wasn't ever in our normal daily builds.We are going to be upgrade our sql server from 2008 R2 to 2014. So i opened the project and upgrade it to a visual studio 2013 project (we hadn't opened it for quite some time). I also upgrade the target framework from 3.5 to 4.5.1. Lastly i changed the target sql server version to 2014. I was able to build it locally. I then tried to add it to our TFS build and got the following error:
E:\Builds\8\TRSApps\Dev\Sources\Shared
Objects\Components\FrsSqlCLR\VB Code\FrsSqlCLR.vbproj (76): The
imported project "C:\Program Files
(x86)\MSBuild\12.0\bin\amd64\SqlServer.targets" was not found. Confirm
that the path in the declaration is correct, and that the
file exists on disk.
I was able to resolve the problem. I searched for "SqlServer.targets" locally and found it under the .net 3.5 framework folder (not under 4.x):
C:\Windows\Microsoft.NET\Framework\v3.5
I just copied it to the location it was looking for it above and it fixed the problems which leads me to my questions:
Is TFS looking for SqlServer.targets in the correct location? If so then why isn't SqlServer.targets there?
Is there something i need to install on the build machine?
Why is the file in the 3.5 framework folder and not in the 4.x framework folder
Though i was able to resolve it by copying it from the 3.5 framework folder it seem a kind of hacky solution. I want the details so in the future when we upgrade our tfs server i have all the details.
You need to install Visual Studio 2013 on the build server. Also Sql Server Data Tools for 2013.
Once you have them on the build server it should build as is.
I currently work on a MVC 4.0 project that was upgraded to MVC 5.0 using the official guide.
I use Visual Studio 2012 locally and a publish profile was created for the project.
Locally I call msbuild via the Visual Studio developer command prompt using: msbuild /m /p:Configuration=Dev;DeployOnBuild=true;PublishProfile=Dev my-solution.sln
All projects in the solutions do have a Dev configuration and there is a web.dev.config.
The command line on the server is the same.
So far the difference is that on the server only the visual studio shell is installed (not the full) and we cannot install the full instance of VS2012 on the server.
Also, seeing on the install of TFS on the server, I discovered that only v9.0 target files were installed (Visual Studio 2008). Copying Visual Studio 2012 target files do not fix this problem.
I see 2 solutions so far but searching for a third.
Install full Visual Studio 2012 instance
Update csproj to include a target transformConfigFiles (basically copy and paste the content of the "Microsoft.Web.Publishing.targets" section) or import the file via a declaration inside of the .csproj
Would there be a third solution available?
It is pretty common to install full Visual Studio on your build server. As of VS 2012 you couldn't even run Unit Tests in your build without VS installed.
I'd suggest installing VS and seeing if that fixes the issue.
I am doing unit tests (no additional frameworks other then what comes out of the box with VS 2013).
It all works locally. What do I need to do to get it working on the build server? The build server is a TFS 2013. There are no visual studio installed other then an 2010 version. I have already moved all the 4.5 .net stuff and .targets files from my visual studio to the build server to be able to compile 4.5 dlls and azure projects.
First I had problem with the build template was using AgileRunner or something thats coming with VS2013. I changed that to MSTest. Is this the correct change? Is there any installers for MSTest only without visual studio that I can install on the build server?
My boss prefers if I can avoid installing Vs2013 on the build server.
Just install Visual Studio on the build server; It is a very common practice. The requirement is mentioned in the installation guidelines. You can have visual Studio 2010 and 2013 installed side-by-side if that is desired. There are so many parts of .NET that depend on it.
Install Visual Studio and other software to enable compilation and other capabilities
You must install on the build agent the version of Visual Studio that your team uses on its dev machines. See Installing Visual Studio. You must also install any other software and components that are installed on your dev machines and that are required to build your app.
http://msdn.microsoft.com/en-us/library/bb399135.aspx#software
You're even allowed to use an existing license for the build server, so there are no additional costs involved if you own an MSDN subscription:
Using Visual Studio on the Build Server
If you have one or more
licensed users of Visual Studio Ultimate with MSDN, Visual Studio
Premium with MSDN, or Visual Studio Professional with MSDN, then you
may also install the Visual Studio software as part of Team Foundation
Server 2013 Build Services. This way, you do not need to purchase a
Visual Studio license to cover the running of Visual Studio on the
build server for each person whose actions initiate a build.
http://www.microsoft.com/en-us/download/details.aspx?id=13350
Is there a specific reason for you boss to not want Visual Studio to be installed?
With regards to the Agile Test Runner, it is the improved test runner that shipped with Visual Studio 2012, it's the replacement of the old MsTest runner, and will replace the old MsTest runner for the last few features for which the old runner is still needed. Though the MsTest runner will still work, certain features will not be as easy to use and confugure (like Code Coverage gathering). The Agile test runner is also required for other test framwork extensibility options, including XUnit .NET, NUnit, but also Javascript Unit Test support (using Chutzpah).
Other features that will require Visual Studio to be installed include:
Code Analysis
Code coverage
MsDeploy / WebDeploy
SQL Server Data Tools
and others.
As an alternative to get just the test runners, you could attempt to install the TFS Test Controller and Agent to the server (you don't need to configure them), the Test Agent will install a number of testing related features without actually installing the Visual Studio Shell.
By not installing Visual Studio on your build server, you are violating the license agreement with Microsoft. Although Microsoft themselves might build without installing Visual Studio on their build servers internally, this scenario is definitely not supported officially.
Building without installing Visual Studio is asking for undefined behavior and jeopardizing the integrity of your builds. I would suggest to stay clear from these attempts until Microsoft officially supports this scenario.
Microsoft strongly recommended not to build without installing Visual Studio when we asked as Gold Partner 2 years back as it was not supported in any way officially and there is no license model covering the scenario.