I need to know whether to work with sharepoint templates I have to have visual studio installed on the server?
No. Developers create solution packages during development and you deploy those solution packages to the server(s) using the Solutions Framework.
See http://msdn.microsoft.com/en-us/library/aa544500.aspx
Related
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.
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 looked far and wide for the answer to this.
In Visual Studio 2013 I can easily create a WebRole and WorkerRole solution but in VS 2015 all I can seem to do is create a Website and WebJob.
Has the WebRole and WorkerRole been removed?
If not can you explain to me where it is - or why it is missing?
Download the Azure SDK for Visual Studio 2015 from here: https://azure.microsoft.com/en-us/downloads/
It should force you to close Visual Studio, but if it doesn't, do so anyways. Once it's installed, you can reboot it.
When you go to add a new project, you can look under Cloud and then choose Azure Cloud Service. This will give you the same old familiar screen, where you can choose a Web Role or Worker Role:
With a new install of VS2015 you have to download and install the Microsoft Azure SDK for .NET - See: https://msdn.microsoft.com/library/ff687127.aspx#Install
Microsoft Azure SDK for .NET extends Visual Studio and to install the Azure tools:
From Visual Studio's menu bar choose File -> New -> Project.
From Installed Templates choose either the Visual Basic or Visual C# node,
and then choose the Cloud node that contains a project template named Get Microsoft Azure SDK for .NET.
Note: This template only appears if you haven’t installed the Azure Tools.
To download the tools, choose the OK button.
An Azure Tools tab appears.
To start the download, choose the Download Azure Tools button to open the web installer.
Follow the instructions provided by the web installer to install the latest version of the Azure tools and the Azure SDK.
Azure Tools requires Internet Information Services (IIS) version 7, 7.5, 8, or Express. To install IIS or IIS Express, use the Microsoft Web Platform Installer.
Note: You might have to restart Visual Studio before the Azure project templates appear.
i created a windows form application in VS2010 using QBSDK.
my problem is that the target has QB installed and running, but i get an error when trying to deploy my one-click application. (the error is just that the application generated an error - and i cannot find the log file to see what actually happened).
to solve it, If i install the QBSDK onto the target machine, it runs fine.
My question is:
what do i need to include in my deployment so i DONT have to install the SDK?
You need to install the SDK redistributable components for any application that uses the SDK to work. If you are using QBFC, RDS or the QBO connector, there are only two supported ways to distribute these components:
1. You can use the stand-alone compressed-image installers that Intuit provides.
2. You can use the merge modules that Intuit provides.
I don't use ClickOnce deployment, but I think that if you are using ClickOnce deployment you can not include merge modules. I think there's a way to create a custom prerequisite that will install using the stand alone installer; http://msdn.microsoft.com/en-us/library/ms165429%28VS.80%29.aspx
If you don't want to go that route, you would need to use another deployment option. In Visual Studio 2010, you can create a Visual Studio Installer Setup Project that you can add the merge modules into. This project type is NOT available in the Express editions of Visual Studio, though.
There is a section in the QBSDK Programmer's Guide that gives some more details about deploying the SDK with your application.
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.