Best points to start understanding WPF data binding are the MSDN articles “Windows Presentation Foundation Data Binding” here and here. More can be found in the MSDN magazine article Customizing Controls For Windows Presentation Foundation. To learn how to bind to element properties the forum entry may help. A somewhat twisted introduction to Styles and Templates can be found here.
A while ago Microsoft release the Consolas Font for Visual Studio 2005. I haven’t thought of it since installed the first time until I set up my machine during the last days. There is a significant difference while using the Consolas font (all characters the same width, optimized for ClearType and quite a bit smaller than the old typewriters). The pictures shows a direct comparison of both fonts…
Another new download featuring WPF examples:
“The Panel is the place to collect showcases of new user experiences and provide insights on how they were implemented. WPF applications and Windows Live gadgets are featured.”
- “New processor support (e.g., Core Duo) for code generation and profiling”
- “Performance and scale improvements in Team Foundation Server”
- “Team Foundation Server integration with Excel 2007 and Project 2007”
- “Tool support for occasionally connected devices and SQL Server Compact Edition”
- “Additional support for project file based Web applications”
- “Windows Embedded 6.0 platform and tools support”
Especially the Core Duo support sound quite nifty to me. However, running Vista you have to wait some more weeks for some additional features.
“For developers using Visual Studio 2005 on Windows Vista, Microsoft is in current development on an update to Service Pack 1 called the ‘Visual Studio 2005 SP1 Vista Refresh Beta’. This update builds on the improvements made in SP1 and delivers a first class experience for developers wanting to take advantages of the new features in Windows Vista. The Visual Studio 2005 SP1 Update for Windows Vista is expected to ship after the consumer availability of Windows Vista in Q1 of 2007 and is now available in bet”
Just in case you are wondering why the two service packs are separated you can find more over here.
Good to know where to find the Pre-released Microsoft .NET Framework 3.0 Uninstall Tool.
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.
Several times I got the question what the vshost.exe is in Visual Studio Express Editions. If you are familiar with Visual Studio the answer is easy: It is called hosting process. And is described in here:
“The hosting process is a feature in Visual Studio 2005 that improves debugging performance, enables partial trust debugging, and enables design time expression evaluation. The hosting process files contain vshost in the file name and are placed in the output folder of your project.”
While working with Web Services in one of my projects, I got some compiler errors: The type of particular namespaces could not be found. Actually, I checked the line and it looked as the namespace – (a Web) reference was not found. However, in the Solution Explorer everything looked fine. If you click the namespace identifier which seems to be wrong, a smart tag appears which allows you to extend the namespace to it’s full identifier. And there you can see, why the compiler finds an error.
Cool feature if you know that it is there.
John Rivard explains why the each Visual Studio does only support one specific .NET Framework.
An article about the Kids Programming Language can be found at the Coding4Fun site.