By default, Visual Studio uses Internet Explorer for debugging. If you’re looking for a way to change that, perhaps to harness the power of developer tools in Firefox or other browsers (or perhaps just because you don’t like IE), it’s pretty easy to do.
Right-click your start-up project in Studio and click Browse With…
Click the Browse button beside Program Name
Select the browser you wish to use
Select the browser you just added and click Set as Default
Here are the install locations of some of the more common browsers:
Firefox: C:Program FilesMozilla Firefox
Chrome: C:Documents and SettingsUserNameLocal SettingsApplication DataGoogleChromeApplication
Safari: C:Program FilesSafari
Opera: C:Program FilesOpera
IE: C:Program FilesInternet Explorer
I find myself using Firefox the most, followed by Chrome. And as a best practice, don’t forget to test your projects in all browsers before putting them into production!
Are there differences in application architecture that are important for the cloud?
It is important to build applications and workloads specifically for the cloud. You will want to carefully consider what services the cloud provider of your choice has to offer and how your application leverages those services.
What’s the benefit of hosting in the cloud vs. traditional options?
Reasons not to host in the cloud are few and far between. If you don't host in the cloud, you will spend more in both CapEx and OpEx to manage your applications or websites in a traditional environment.
How can I improve the performance of my application?
There are several primary reasons that applications perform poorly, and in some cases it’s a combination of several. 1) Data latency: If your application is making calls to a data source (whether it’s an API or a direct call) and there is latency at the data provider, your application performance will suffer.
The answer is ‘probably yes’. There aren’t many reasons for an application to be hosted elsewhere, aside from occasional compliance standards, or requirements to integrate with local services that would require large amounts of data to move from on-premise to cloud.