Tech Master- live to innovate

  I have seen a few articles on creation of a hosted service using C#.  Most articles describe creation of a hosted service in a cloud environment very nicely. But this article will explain creation of a hosted service in Azure as well as some error descriptions. (I struggled a lot, while adding a certificate, accessing a certificate and resolving the errors conflict error, bad request (400) and hosted service name is invalid etc.). I would like to mention a few things in here related to creation of a hosted service: Service Name; actually a service name will be assigned to the DNS Prefix property in the cloud staging or production environment. It is recommended to have a minimum of four to five characters. According to Azure standards, we should add "DNS" as a prefix with the service name. It should not contain the "/","\","." characters. It does allow the "-" character. The text assigned to the label field will be used as the hosted s...

  Using Windows Azure SDK 1.3 or later we have the ability to launch a process (called a startup task) like: Before a role starts and the role will be started after the completion of the task. A Role will not wait for a startup task to finish, instead it will launch just after the startup task is executed. Both role and startup task would be independent. We can run a role as long as the startup task is running. To add a startup task, we need to include the following lines of code in the service definition file (.csdef) as shown below. <ServiceDefinition  name = "MyService"   xmlns= "http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceDefinition" >   <WebRole  name = "WebRole1" >   <Startup>   <Task commandLine= "Startup.cmd"  executionContext= "limited"  taskType= "simple" >   </Task>   </Startup>   </WebRole>   </ServiceDefinition...