Not much time for doing a lot of other stuff, since I am just working on a paper for Pervasive 2007.
“Acousmêtre… is a French word for Acousmêtre”
During ICEC 2006 Conference
The latest CTP of the Robotics Studio is available for download. Finally, the part my Colleague Andreas Ulbrich is working on is integrated for testing. Using dssnewservice.exe offers a new feature but there are some changes necessary to be done in the created code also shown on Channle9.
If you create a new DSS service for Microsoft Robotics Studio that is not located within the MSRS directory you have to adjust some minor settings in Visual Studio 2005. You will realize dssnewservice.exe is a very helpful tool to create new services. If you follow the instructions below, you can set up new services within less than a minute if they are not located within the MSRS directory.
The first you should set some more environment variables to your system to make development much more convenient. Extend the PATH system variable in System Properties / Environment Variables / Edit User Variable to %PATH%;C:\Program Files\Microsoft Visual Studio 8\SDKv2.0\Bin;C:\Microsoft Robotics Studio (August 2006)\bin;C:\WINDOWS\Microsoft.Net\Frameworkv2\v.0.50727
The first is not necessary but makes life easier, e.g. when you want to call tools such as ildasm.exe from command line. The second gives easy access to dssnewservic.exe. The last path is required to use dssproxy.exe later during compile time to gain access to msbuild.exe.
Create a new DSS service
Go to the folder where you want to create the new service. E.g. in C:\Documents and Settings\aheil\My Documents\Visual Studio 2005\Projects\MySolution you can type
> dssnewservice /namespace:My.Namespace.MyProject /service:MyService
Now add this project in your Visual Studio solution. right-click your solution in Solution Explorer and choose Add / Existing Project … Browse to the service created before and choose MyService.csproj.
Setup Project Properties in Visual Studio 2005
Now you can easily set up the properties. Chose Project / MyService Properties … to open the properties tab.
- Chose Application and adjust the assembly and namespace name you prefer.
- Chose Build and adjust the Output path. MSRS assumes that you create the service within the MSRS folder. So chose C:\Microsoft Robotics Studio (August 2006)\bin\services to cause Visual Studio to copy the files to the appropriate location.
- Now modify the build events. Since dssnewservice.exe assumed your project to be located in the MSRS directory, the path for the signing keyfile is pointing to a wrong place. Either correct the path to the sample .snk file or use a path to your own key file to sign the proxy assembly. If you don’t, this will result in a error code -1 by the dssproxy.exe during compile time. When the proxies are created msbuild.exe is used. that was by the way the reason to add the third path at the beginning to your environment variables. Otherwise you get a code 3 by the dssproxy.exe.
- You will realize, the CRR and DSS references are not available within your project. Instead of removing and adding them again, just select the Reference Paths tab. There browse to the folder C:\Microsoft Robotics Studio (August 2006)\bin and press the Add Folderbutton.
- Finally sign your assembly. Chose the Signing tab, check the Sign the assembly box and select <Browse>to chose a keyfile to sign.
- Press F6 and compile your solution.
I’ve tried these steps with several projects, so these steps should also work for you. If you encounter any problems drop a comment. Please be aware of the fact that you follow these instructions on your own risk. So don’t blame me if anything does not work like expected. Also this is not a official support article of Microsoft or the Robotics group. I did write this in my spare time to share some experience with the MSRS community. Also, these steps are supposed to work with the August 2006 CTP of the MSRS.
Why (and how) IE is restricted in simultaneous downloads is described in the knowledge base.
“WinInet limits connections to a single HTTP 1.0 server to four simultaneous connections. Connections to a single HTTP 1.1 server are limited to two simultaneous connections. The HTTP 1.1 specification (RFC2616) mandates the two-connection limit. The four-connection limit for HTTP 1.0 is a self-imposed restriction that coincides with the standard that is used by a number of popular Web browsers.”
Since I have the new XDA Trion am willing to investigate into UMTS. The first the UMTS coverage – as one can see, the right top corner appears in light blue and seems to be not covered.
There was some trouble in activating the UMTS with O2. Actually they send a new SIM card with the phone. Until this card is activated, you can’t change the options (including UMTS). Activating the new card would lead to the deactivation of my multi cards. After asking the support (that’s the advantage being a “pay monthly” customer) it took only a few minutes to cancel the new card’s activation. Just adding the UMTS option within the portal is the secret.
Finally, it is not as easy as I thought: adding the UMTS option includes a pair of new UMTS enabled SIM cards. Even if your old ones support already UMTS. Now I have to wait until the new cars are activated.