![]() Microsoft Visual Studio 2010 Professional is huge, sprawling, and expensive, on the one hand, but surprisingly intuitive and nimble on the other. NET Framework dependence and prefer Visual Basic 6.0. Performing without a (dot)NET: Some developers have expressed frustration with Visual Studio's. It's a lot to install, and to remove, too, if you choose not to buy. NET Framework, but needed Microsoft Application Error Reporting, VC Runtime 10 (圆4 and x86), and Microsoft Visual Studios 2010 64-bit Prerequisites (圆4). Our 32-bit system already had VC Runtime 9 (x86) and. Needy: Visual Studio requires some additional components to do its job. ![]() You may be able to do without some components, such as SQL Server or Sync Framework. Space eater: Visual Studio's primary installation needed 6GB of disk space. Going Pro: Visual Studio gets right down to business with quick access to server links, New or Existing Projects, and essential resources and communities. We like being able to specify which tools and programming languages to install and the individual disk space requirements for all of our drives.Įxecutive suite: Visual Studio has specific settings for different areas of development work, starting with General Development and including Project Management, Web Development, and various programming languages.Įasy on the eyes: A classic Explorer layout with easily accessible and pin-able sidebars (like the right-hand Solutions Explorer) and Office-like touches make Visual Studio not only familiar but also surprisingly easy to manage for such a large suite. It takes up several gigabytes and costs $799, but you can try it free for 30 days.Įasy ins: Visual Studio's compact download manager greatly eases the process of downloading and installing this 3389.6MB package. Your subscription will have been chosen assuming you have already taken care of all of that before by signing up for azure, you then click on the Browse button and then paste in your directory, you will probably have to clear out the certificate key filename to allow you to open the directory to choose the file, then ok that and then ok this screen and you will have your app authorized for azure.įinally you can go back to studio and click on your ok button to publish your app to azure, it does take a while and the progress of the publish will show up in the lower section of studio in the activity log.Microsoft's Visual Studio 2010 Professional is an integrated solution for developing, debugging, and deploying all kinds of applications. Then just click on the “Add Certificate” button ![]() In the azure portal, locate the “Management Certificates” under “Hosted Services, Storage Accounts and CDN”, click on that and you will see something like this below. When you get that created, you can click on ok and you are almost ready to publish your app to azure.īefore you click OK on the next screen, over in your Azure portal, you need to make sure to upload your certificate to Windows Azure so that your app will be authenticated with the server. ![]() You can make your certificate in this screen and then use the “Copy the full path” link there to get it copied to the clipboard and then you will also need to get your subscription ID from the Windows Azure portal, you can find that under “Hosted Services” under the right hand pane in the “Subscription ID” box. You will need to create a Certificate by dropping down the Credentials dropdown and then hitting “New”, that will bring up a screen like this: The next step you will see a screen like this: The first thing to do is open your project in Visual Studio 2010 and right click on your Azure Project and click on Publish: You have to make sure you have a Windows Azure account of course to go through this tutorial I have here as well, again, pretty self-explanatory. I am not going to go into the creation of the app, just the publish part of it, there are tons of examples out there that go into details of how to create your app and there are several example apps you can download as well. Here is the steps I took to get my app actually published to Windows Azure, hope it helps. This is very well likely due to the fact that things have changed over the course of the last year or so with Windows Azure. I have been tinkering around with Windows Azure using Visual Studio 2010 and I am finding that more and more of the articles you find on the internet are either outdated or just wrong.
0 Comments
Leave a Reply. |