Motivation Behind the term Azure
Features of Windows Azure
Checking the Health Status of Windows Azure services
Great Azure Example
Windows Azure Platform site
Azure Pricing
TCO Calculator
Connecting with SQL Azure through SSMS
Monday, May 24, 2010
Talk on windows azure
This is the talk session held on Sunday 23rd May 2010 in the Pearl Solutions LLC's conference room at 14040 NE 8th ST Bellevue WA.
Presenter- Vidya Vrat Agarwal
Attendees - Anubha, Kajal, Nanjunda, Sumeet, Varun, Madhuri and Swathi.
Presenter- Vidya Vrat Agarwal
Attendees - Anubha, Kajal, Nanjunda, Sumeet, Varun, Madhuri and Swathi.
Wednesday, May 19, 2010
Talk on Windows Azure
Date - Sunday 23rd May 2010
Agenda - This session will discuss the emerging Microsoft technology named Windows Azure. Its features, technical jargons associated with it and what are the scenarios it best fits into.
Location - 14040 NE 8th St Bellevue WA 98007 (Pearl Solutions LLC conf room)
Start Time - 12:45 PM
End Time - 1:45 PM
Contact Person - Vidya Vrat Agarwal
Contact Number - 425-516-2058
Agenda - This session will discuss the emerging Microsoft technology named Windows Azure. Its features, technical jargons associated with it and what are the scenarios it best fits into.
Location - 14040 NE 8th St Bellevue WA 98007 (Pearl Solutions LLC conf room)
Start Time - 12:45 PM
End Time - 1:45 PM
Contact Person - Vidya Vrat Agarwal
Contact Number - 425-516-2058
Saturday, May 15, 2010
CLS Compliance - Problem Scenario & Solution
CLS (Common Language Specification) is a very important component of .NET architecture. CLS complaince helps language-interoperability to take place on a common ground, so an application written a any .NET compliant language can be exposed other application writtent in a .NET compliant language.
Scenario:- Consider you are building a C# dll, which is going to be used by .NET client application written in VB .NET. By nature C# is case-sensitive and VB .NET is case-in-sensitive.
Due to this specific casing behavior of these languages, C# has power to declare class members (methods, variables etc) in case-sensitive manner. I.e Deposit(), deposit() and dePosit() are three different methods which can be created in C#.
But this is not how VB .NET works. VB .NET can't allow this because VB .NET is case-insensitive and so can't differentiate that these are three different methods.
Problem:- The problem occurs when the C# dll is being consumed by a VB .NET, and so none of the functionality from C# is exposed to VB .NET, even though its successfully built in C#. Reason of this is that VB .NET don't see those methods of C# as three different methods and so can't decide which one to display in the Intellisense.
Solution:-
The solution of this problem has to take place in C#, because C# has case-sensitive nature.
If you are building a reusable dll which can be easily consumed by any .NET compliant language eveb by those which are not case-sensitive like C# in which the dll has been developed.
You need to enable the CLS Complaince in C# application, by default its set to false.
Once you enable it then any member of a class which differs by case is listed in the CLS-complaince warning.
Now the fix for this is to resolve these CLS warnings and fix the function names, lets rename them rather being different in case only.
After the change in function's name, now there are no member functions in the C# class which differs by case only.
Now VB .NET client can see these functions
Scenario:- Consider you are building a C# dll, which is going to be used by .NET client application written in VB .NET. By nature C# is case-sensitive and VB .NET is case-in-sensitive.
Due to this specific casing behavior of these languages, C# has power to declare class members (methods, variables etc) in case-sensitive manner. I.e Deposit(), deposit() and dePosit() are three different methods which can be created in C#.
But this is not how VB .NET works. VB .NET can't allow this because VB .NET is case-insensitive and so can't differentiate that these are three different methods.
Problem:- The problem occurs when the C# dll is being consumed by a VB .NET, and so none of the functionality from C# is exposed to VB .NET, even though its successfully built in C#. Reason of this is that VB .NET don't see those methods of C# as three different methods and so can't decide which one to display in the Intellisense.
Solution:-
The solution of this problem has to take place in C#, because C# has case-sensitive nature.
If you are building a reusable dll which can be easily consumed by any .NET compliant language eveb by those which are not case-sensitive like C# in which the dll has been developed.
You need to enable the CLS Complaince in C# application, by default its set to false.
Once you enable it then any member of a class which differs by case is listed in the CLS-complaince warning.
Now the fix for this is to resolve these CLS warnings and fix the function names, lets rename them rather being different in case only.
After the change in function's name, now there are no member functions in the C# class which differs by case only.
Now VB .NET client can see these functions
Subscribe to:
Posts (Atom)
