I am trying to create a webproject which can be deployed on azure. I have VS 2010 trial version (pro) installed on windows 7. When i click cloud (under VC#) i am prompted to install Windows azure tools. I do this. I get the tools installed message. I restart VS 2010. But i fail to find windows azure web project template, which should have been installed. It just shows me the same sequence of screens (install tools etc). I am executing VS 2010 under administrator role.
Steps described # http://msdn.microsoft.com/en-us/library/windowsazure/ff687127.aspx
Questions
Is Windows azure template projects not allowed in Trial edition of VS 2010 pro?
Can such a project be made using VS 2010 express?
Thank you
Sameer
I'm not sure about trial versions, as I've never tried installing with a trial edition. However: I've run other software packages with trial versions of Visual Studio, without issue.
The SDK will work with Visual Studio 2010 Pro and above, as well as Visual Web Developer 2010 Express (downloadable here).
For installing the tools properly, I'd suggest going here and installing via Web Platform Installer. It will make sure you have all needed dependencies.
Related
I rent absolutely free
Edition Windows 10 Pro
Version 20H2
Installed on 2/7/2023
OS build 19042.1706
Experience Windows Feature Experience Pack 120.2212.4170.0
With Excel installed and Activated by hosting provider
Microsoft Office LTSC Professional Plus 2021
Version 2108 (build 14332.20447 Click-to-Run)
Than I try to install to this new machine VS 2022 community from official site
Unfortunately VSTO tools is impossible to install, I see a lot of times the same error
VSTO installation Error
What I need to do? I need VSTO.
I receive advice to download firstly and install after full download. In this case I have this error.
Something going wrong
What going wrong I don't understand. This VM placed to datacenter in Germany with good connection and preinstalled and activated legal copy Windows 10 and Excel.
Most probably you are dealing with a connection problem. You may try to repair your VS installation at a later point of time.
You may consider downloading a local installation package, select the Download all, then install option in the dropdown at the bottom of the Workloads tab of the Visual Studio Installer. The purpose of this feature is to frontload the downloading of the Visual Studio packages onto the same computer that you plan on eventually installing Visual Studio on. By downloading the packages locally first, you can then safely disconnect from the internet before you install Visual Studio.
Also you can download the installer locally by using a command line. And only then you can launch the installer for the Visual Studio, so you will not face with such problems. Read more about that in the Create an offline installation package of Visual Studio for local installation article.
Can we use MSBuild without Visual Studio 2012?
Currently, we have a build server where we are compiling and creating deployment copy of one of our projects, it has Visual Studio Professional Edition installed. We are setting up a new build server now. Do we really need Visual Studio 2012 on the new build server?
If yes, then how? I googled it but I couldn't find an answer.
We have spent a lot of time trying to get our Build Servers to work without Visual Studio.
We do not use TFS for builds and therefore I am not sure the license exemption above applies to us. Also not having Visual Studio installed helps you really understand how your software is building and get references correct.
We have seen many examples of solutions with projects that contains references for the same piece of software with some in nuget packages shipped with the solution and others that are pointing to locations in the "program files" path which are not present on machines without Visual Studio installed. Once you attempt to build software without VS installed you can really see how "self-contained" your applications are.
Before I start listing the things you typically need to install, let me just point out that MS Build is now no longer considered part of the .NET framework but is shipped with Visual Studio but can also be installed separately. See this blog post for more: http://blogs.msdn.com/b/visualstudio/archive/2013/07/24/msbuild-is-now-part-of-visual-studio.aspx
The following software needs to be installed for most builds, there may be others for example if you are creating portable class libraries.
Microsoft Build Tools 2013
Web Deploy 3.5 (for packaging applications)
Microsoft .NET Framework 4.5.1 Developer Pack
Microsoft .NET Framework 4.5.2 Developer Pack
Windows Software Development Kit (SDK) for Windows 8 (You can use the SDK to build applications that target these operating systems: Windows 8, Windows 7, Windows Vista, Windows Server 2012, Windows Server 2008 R2, Windows Server 2008)
The following directories need to be copied:
Reference Assemblies (need to be copied from a machine running Visual Studio from/to directory C:\Program Files (x86)\Reference Assemblies)
Public Assemblies (need to be copied from a machine running Visual Studio from/to directory C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\PublicAssemblies
We also use Wix and therefore we install the following:
WIX Toolset 3.8
I have a similar set for testing however that was not part of the question so I will leave that off!
Hope this helps someone.
Update: 3rd March 2017
Microsoft recently responded to a long standing user voice request "Support .NET Builds without requiring Visual Studio on the server" for the requirement for Visual Studio to be installed on a build server to be removed.
From the description on the download page "These Build Tools allow you to build native and managed MSBuild-based applications without requiring the Visual Studio IDE." Not tested yet but after RTM I will look at this and provide a further update here.
There is a blog post that promises these build tools install all pre-requisites and can be used to build MS Build based applications.
No, you don't need Visual Studio on your build box. If I recall correctly, msbuild is installed as part of the .NET framework - it certainly used to be.
Depending on what you're building, you may find that there are some things which are easier to get working if you do install Visual Studio though - things like portable class library profiles. While there are usually non-VS installers available, I've found it simpler to install an Express edition of Visual Studio just to get the bundled build targets.
Remember: The easiest way to build your visual studio solutions is to install Visual Studio on the build server. Even Visual Studio Express is often enough.
That said, you can make it work without it. But it it sometimes a lot of work to figure out. You'll need to install the right Windows / .NET Platform SDK. You can install multiple of these SDKs side by side. Now, when you depend, for example, on ASP.NET MVC 5 or Entity Framework 6, you might need to install further SDKs to get your application to compile. The downloads for these all assume that you also have Visual Studio installed, but many of their payloads can also be installed separately. It can become quite a hassle.
Personally I've grown tired of trying to figure out which parts of which installers enable what. But that is also driven by the fact that Microsoft allows you to install Visual Studio on a build server (TFS) with the same license as your development machine as long as you are an MSDN subscriber. Check the Visual Studio License Whitepaper for more details.
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.
If you, like me, would prefer this to change in the future, I suggest you make sure you're heard by submitting your request or voting for an existing one over at the Visual Studio User Voice.
Here's just a quick take on this.
Your build machine should decouple development tools as much as is possible. With that said, and as already stated by others here, MSBuild can be run independently of Visual Studio, and it should!
If your build requires Visual Studio to run then there is a very good chance that you have a solution or project architecture problem that ought to be resolved.
Visual Studio doesn't need to be installed. MSBuild is part of the .net SDK.
Other .net dependencies will need to be installed though, if you are using them. MSTest, or anything that is part of Team foundation will require Visual Studio installed.
I believe you only need MSBuild ( that is part of the .NET framework you're targeting ) .
Make sure you install the proper .NET distribution
the following is a good place for build servers it have the developer tooling.
The .NET Framework 4.5.1 Developer Pack installs the multi-targeting pack for .NET Framework 4.5.1. Developers can build applications targeting the .NET Framework 4.5.1 using either Visual Studio 2012 or third party IDEs. You need to download the web installer instead of this package if you intend to redistribute .NET Framework 4.5.1.
http://www.microsoft.com/en-us/download/details.aspx?id=40772
Best of luck.
C++ :
There is a "Build Tools" that contains MSBuild, Visual studio is not required.
From the official doc :
These tools allow you to build C++ libraries and applications
targeting Windows desktop. They are the same tools that you find in
Visual Studio 2015 in a scriptable standalone installer. Now you only
need to download the tools you need to build C++ projects.
Managed :
The same applied : Build Tool Managed
I just installed visual studio 2012 professional (with Blend) and now I can't open a .NET MVC3 web project. The project does not load and says it is incompatible, despite the fact that other developers working on the same codebase are using VS2012 with no issue.
Furthermore, when I go to Solution -> Add -> New Project, I don't see the option to add a web project that I did with VS2010. This makes me think that I am missing some kind of web developer setting, extension, or add-in, but I can't figure out how to install that.
How can I fix my visual studio (or project) setup to allow me to open this project?
You do not appear to have installed a web version of visual studio.
I'm guessing you installed the Express version of either the Windows 8 Edition (which creates Windows 8 apps) or the Windows Desktop version (or maybe Windows Phone version).
If this is the express edition, download and install the Web Edition. If this is a Professional or higher version, then you may not have installed the right components.
According to Microsoft the side-by-side installation of Visual Studio 2010 and 2012 is supported (http://msdn.microsoft.com/en-us/library/ms246609.aspx).
I already had VS 2010 installed on my system (Windows 7 box) along with the Windows Azure Tools 1.5. I used this configuration to create a cloud project that is hosted on Azure. A few days ago I decided to also put VS 2012 on my system but to do it in a side-by-side manner rather than upgrading (or uninstalling) the VS 2010. The reason why I did not want to uninstall VS 2010 was that I already had some add-ons configured for it for script and css minification and aggregation. I heard that VS 2012 has this functionality built-in but I did not want to touch the dozens of scripts that I had already created using the older method. So I wanted to keep my VS 2010 environment in a pristine, working state in case there was an emergency and I had to publish a patch for my already hosted application. I would use VS 2012 for all the new projects going forward.
However, after I put VS 2012 on my box it also brought down 1.8 version of Azure SDK. As a result, I can no longer successfully build my VS 2010 solution. I have one worker role and one web role in that solution. If I build each one of them individually the builds succeed. But if I then try to build the entire solution or package it, it fails with no message in the log whatsoever. It just shows "Build Failed" in the VS status bar.
Since I was not getting any error in the status bar, I decided to create a "Hello World" application from scratch with only one web role using Windows Azure Cloud project template in VS 2010 hoping to get a better error message. Indeed, when I try to build the entire solution I get an error:
Error 102 WAT080 : Failed to locate the Windows Azure SDK. Please make sure the Windows Azure SDK v1.5 is installed. C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\1.5\Microsoft.WindowsAzure.targets
Clearly the installation of VS 2012 and Azure SDK 1.8 corrupted the older version. Ideally I would like to keep VS 2010 + Azure SDK 1.5 truly side-by-side with VS 2012 + Azure SDK 1.8. Is there a way to do this? If not, then how can I fix the error above? In other words, how can I fix VS 2010 to work with Azure SDK 1.8?
All you help is greatly appreciated.
Regards,
Archil
I solved this by going to Microsoft site and installing Windows Azure SDK for .NET - October 2012 (1.8).
http://www.microsoft.com/en-us/download/details.aspx?id=35448
Initially I was a bit afraid and people were saying that it would not work and they encouraged to do a manual one-by-one install. However, I decided to use the Web Platform Installed link from the above page:
http://go.microsoft.com/fwlink/?LinkId=254269
All in all, things went smoothly.
Is Windows Phone 7 Development SDK available for other versions of Visual Studio 2010 than Express?
If I already have the Ultimate version do I still need to download VS2010 Express to use WP7 SDK?
When you install the Windows Phone 7 SDK it installs everything including "Visual Studio 2010 Express for Windows Phone" even if you have another non-express version of Visual Studio 2010 already installed.
If you have another version of VS2010 installed. the installer will NOT create any shortcuts for the express version. Nor will it set any file associations for it.
This has two effects:
The installer is simpler (It just gets everything and only needs logic around setting shortcuts) and so should be less buggy. - Most people have no issues with it. The few who do have problems have mostly fixed them with a repair of the install.
You can use both the Express and other version of VS2010 on the same machine. I find this particularly useful when looking at open source or demo projects which were created with the express version.
The WP7 environment will install into your existing instance of Visual Studio if you have one (and will install an Express edition if you don't)
Yes, you would need to download the full SDK. But nothing to worry since installing the SDK would automatically take care of installing the templates, and you should be able to work with your Ultimate edition with all the goodness :)
Microsoft could verify that the Visual Studio (not Express) is already installed on the machine BEFORE you download the Express version!
Still, the Express version does not interfere with your other version of Visual Studio.