If you’ve installed the VS.NET 2005 beta 2, and you are going to use it for Visual Basic programming, you might like the fact that DevExpress has created a free refactoring plugin. You can read more about it here, download it here. This add-in is a very important one, after the announcement that VB.NET2005 will not include refactoring (at least not the full monty).
In the EMEA region the Visual Studio .NET 2005 beta experience has started: you can now order beta 2 of the upcoming IDE.
One of the findings in this post is “Micro ISVs are not on the cutting edge of technologies”. Didn’t these people hear ALL Micro ISV’s cry when the new pricing of VS.NET 2005 (especially Team Studio) became public? How can a Micro ISV support cutting edge technology, if buying into it means such a big risk? How can we test solutions for IIS 6 if we have to buy a new OS first? Why does Office change with EVERY version? Perhaps you (John) should not be asking “where are the Micro ISV’s”, but instead you should count the increase in development in the oh-so dangerous Open Source scene. Look at the number of one-man-bands that provide paid support for some kind of Open Source CMS. It pays good money, you don’t have to write or maintain the software yourself, and webapplications, hey, that’s the new hype so lot’s of companies are willing to hire you. John? You there?
Microsoft release both the redistributable and the SDK of beta 2 of the .NET Framework 2.0. And making things utterly complete, you can choose between 32 and 64-bit (IA64 and x64) editions. Click on the title to go to the downloadpage.
Most people would want the 32bit versions. The SDK is about 317MByte, the redist is about 23MByte, and as before, you need the redist before you can use the SDK.
I stopped using .Text as my blogging engine a long time ago. Here’s a screenshot why. In case you didn’t know: Scott is the CREATOR of .Text.
When you need to create some temporary files, you can create them in %TEMP%. If you don’t delete them yourself, some other program or the user will, since the directory defined in %TEMP% is meant to store TEMPORARY files.
Now read this post about the Visual Studio 2005 Team Foundation Server beta 2 setup. Tell me they are not seriously blaming the anti-virus software for deleting files from %TEMP%? Guys, this is Microsoft not knowing where %TEMP% is for. How f*cked up is that? Any decent installation program that needs a reboot creates a folder somewhere on C:, and deletes this folder after the reboot is done and the installation has completed. Not Microsoft: please disable your Antivirus software if you’re going to install TFS. This is seriously wrong. I sure hope they will have their act together before the “release”.
This post is just to claim my blog on Technorati. You can view Technorati profile here.
Perhaps this category will have obvious solutions or tips, but I’ll share them anyway: C# code snippets. This first one is about logging on to Outlook, which I needed for E-Sync. All samples give you the code with the name of the profile to logon to, or “leave the values for profile and password blank to use the default profile”. The first one means hard-coding a profile, the second one I did not get working on 2 different machines, so I guess it used to be like that but not anymore.
Here’s how to lookup the default profile in the registry, and logon to the MAPI-store.
RegistryKey myKey = Registry.CurrentUser;
myKey = myKey.OpenSubKey("SoftwareMicrosoftWindows NTCurrentVersionWindows Messaging SubsystemProfiles");
String myProfile = myKey.GetValue("DefaultProfile").ToString();
myMAPISession.Logon(myProfile,"",true,myMV,myMV,myMV,myMV);
Don’t forget to include “using Microsoft.Win32;”.
The appointments from the ERP-application come in two flavours. A “real” appointment, with attendees and a real date and time that it occurs. And a “structure” appointment. Only very basicly defined occuring on a certain weekday (Friday, from 9:40 – 10:00 am). The “structure” appointments are filled in later, but they are used by the planning department to see what the employees have designated their timeblocks to.
E-Sync now differentiates between real and structure appointments, also marking the structure appointments as “free”, instead of busy.
What I need to do before the first release is:
– Read attendee information from the database. Their unique number is not informative enough
– Save the entered values for next time E-Sync starts (and don’t show the defaults anymore)
– Make the colors per appointmenttype configurable
The first release is planned for May, 2nd (that’s a Monday). Very exciting.
The PIA’s (Primary Interop Assemblies) for Office 2003 are now available as seperate download, so if you’re a developer, and don’t have Office 2003 (that includes the PIA’s), you can now download them and target your application at Office 2003. You can find them here. They are Microsoft .NET Framework version 1.1 assemblies.