Windows Azure Biztalk Services: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

While deploying Biztalk Services to Windows Azure, you may get the following exception.

The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

To resolve this issue download the SSL Certificate from the Azure portal and import to local machine Trusted Certificates.

Steps to download and import certificate to local machine:

1. Go to biztalk service from management portal
2. Click on Dashboard
3. Download SSL Certificate
   
4. In run type certmgr.msc 
5. Go to Trusted root certification authorities -> Certificates
6. Right click on Certificates=>All tasks => Import
   
7. Select downloaded certificate file and click on next=>next to import the certificate
8. You will get an alter message that Imported successfully.

The 'RadLangSvc.Package, RadLangSvc.VS, Version = 10.0.0.0, Culture = neutral, PublicKeyToken = 89845dcd8080cc91' failed to load

A couple of days ago, using the Schema Compare tool included in Visual Studio 2010 Ultimate, I ran into an error that reads:

"The 'RadLangSvc.Package, RadLangSvc.VS, Version = 10.0.0.0, Culture = neutral, PublicKeyToken = 89845dcd8080cc91' package did not load Correctly."

The system continues to operate apparently, only after the settings when we kick off the comparison, the environment crashes fatal.
After a little 'research I found this post which in turn refers to that.

The problem is essentially due to the installation of SQL Server 2008 R2, which affected various components associated with the SQL scripting. The same symptoms occur it is also using the SQL shell included in VS, even though I had installed the R2 for a while, 'I have not noticed it before because I always use the environment to SQL Server Management Studio.
The proposed solution is to simply re-run the post installation

DACProjectSystemSetup_enu.msi

located on the installation disc in the folder of VS 2010

\ WCU \ DAC

but for more serious problems may need to rerun the other two in the same folder installer

TSqlLanguageService_enu.msi
DACFramework_enu.msi

take care of it in VS closed and once the installation is complete, there is no need to restart everything is already back in place.

Unable to launch the application because port 'N' already in use.

I had a similar problem.  I found it to be related to the Eset personal security (guessing a recent update messed something up). To solve it I excluded VS2008 from the active browser filtering - this is in: setup -> advanced firewall setup -> antivirus & anti spyware -> web access protection -> HTTP -> webbrowsers

Deselecting vsdev in here fixed the problem - interestingly enough disabling the firewall and antivirus / antispyware did not solve the issue, so it is worth looking for a similar setting if you are running different security software

HTML 5 Intellisense for Visual Studio 2010 and 2008

You all probably know that new HTML 5 standard is came in the market. A new intellisense schema that you can add to VS 2008 or VWD Express 2008 or VS2010 and get intellisense and validation on HTML 5 elements.
Note that schema is for markup only, we do not have DOM2 update for jscript intellisense yet.

Steps to install the schema:

1. Download Visual Studio intellisense for HTML 5.
2. Place html_5.xsd in C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\Packages\schemas\html for 64-bit OS and Place html_5.xsd in C:\Program Files\Microsoft Visual Studio 9.0\Common7\Packages\schemas\html for 32-bit OS
3. Run either x86 or x64 reg file depending on the OS and VS/VWD flavors installed. For example, for VWD Express installed on 64-bit OS run HTML-5-Schema-Reg-x64-VWD.reg and for VS 2008 installed on 32-bit OS run HTML-5-Schema-Reg-x86.reg.
4. Restart Visual Studio
5. You can select HTML 5 in the target schema dropdown and HTML 5 element attributes should appear in the Properties window.

Schema is experimental and has certain limitations.For example, VS 2008 and VWD are not able to validate 'wildcard' attribute names, like HTML 5 data-* attributes and is not able to handle 'transparent' content model when element content is defined by the element parent (see, for example, A element). However, it may help you to start playing with the new standard.

Debug Sql Server Stored Procedures in visual studio

These are the following steps required to debug stored procedure in visual studio

1. Go to Server Explorer (Visual Studio --> View menu --> Server Explorer),


2. Right click on Data Connections --> select Add Connection,


3. Here type sql server name and select authentication type(windows or sqlserver), and then type your database. Click ok. Now you are connected to sql server.


4. Select a SPROC and Right click on stored procedure --> select Step Into Stored Procedure.


5. Select a SPROC and Right click on stored procedure --> Execute--> Give the default values to debug. Now it starts Debugging.