Archive for the '.NET' Category

DPack for Visual Studio 11 update status

Just wanted to post a VS11 update status. After the conversion all features worked fine out of the box for the most part. I ran into browser features dialog mode problem, which I was able to figure out eventually. I did run into a showstopper with Bookmarks feature though. Bookmarks images aren’t drawn correctly or not at all, and no errors are returned from VS SDK afaict. I’ve submitted a bug report a few weeks back and heard… nothing back from Microsoft once the test case’s been provided. That’s what’s been preventing me from releasing a beta version.

My bug submission is right here on Connect:

The way Connect works supposedly is that they look at number of submission votes and if it appears to be high enough it gets looked at and resolved presumably. So, I’d appreciate if you guys hit the link above, you’ll need to sign in, and cast your vote. This will hopefully get things moving for all of us.


My first published MSDN Magazine article

The article is called “Bring Windows Desktop Search Into Visual Studio With Our Cool Add-In”. It’s about Visual Studio 2005 add-in development and Windows Desktop Search integration. Check it out right here:

It should be in July 2006 issue and available in stores early June. Hope you all like it.

Sergey @ USysWare

.NET developers in today’s job market

Not surprisingly to me, .NET developers are expected to be in high demand this year. According to this “5 careers: Big demand, big pay” CNN article, IT .NET developers along with QA people are in the right spot.

Sergey @ USysWare

Visual Studio Text Markers w/o VSIP

One of the reasons for converting DPack from a collection of add-ins to a single VSIP package was to gain access to text markers. Numbered Bookmarks feature utilizes that with text marker being bookmark images shown in the Visual Studio gutter.

In his post Alex shows how to use text markers with add-ins, i.e. w/o VSIP. Keep in mind, that while you can get to the markers already exposed by VS, AFAIK there is no way to create brand new markers with add-ins. You’d still need VSIP for that.

Here’s his Text Markers article.

Sergey @ USysWare

Step by step Whidbey Beta 2 or CTP uninstallation

Here’s what had worked for me but your mileage may vary.

Using Add/Remove Programs, uninstall Beta 2 or CTP in this particular order:

  • Remove “MSDN Library for Visual Studio 2005 Beta”
  • Remove “Microsoft SQL Server 2005 Express Edition”
  • Remove “Microsoft SQL Server 2005 Tools Express Edition”
  • Remove “Microsoft SQL Native Client”
  • Remove “Microsoft Visual Studio Tools for Office System 2005 Runtime Beta”
  • Remove “DMA Transport Update for VS 2005 Beta 2″
  • Remove “Microsoft Device Emulator 1.0 Beta”
  • Remove “Microsoft .NET Compact Framework 2.0 Beta”
  • Remove “Microsoft Visual Studio 2005 Professional” or (Standard/Enterprise Architect/Team Suite, etc.)
  • Remove “Microsoft Document Explorer 2005 Language Pack”
  • Remove “Microsoft Document Explorer 2005″
  • Remove “Microsoft SQL Mobile 2005 Development Tools”
  • Remove “Microsoft MSXML 6 SDK and Parser”
  • Remove “Microsoft Visual J# .NET Redistributable 2.0 Beta Language Pack”
  • Remove “Microsoft Visual J# Redistributable Package 2.0 Beta”
  • Ensure all Visual Studio 2005 products have been removed from your system
  • Remove “Microsoft .NET Framework 2.0 Beta Language pack”
  • Remove “Microsoft .NET Framework 2.0 Beta”

Continue with the following post uninstallation manual clean up (* implies ‘any name’):

  • Delete HKLM and HKCU Software\Miscrosoft\VisualStudio\8.0 registry keys
  • Delete “\Documents and Settings\YourProfileName\Application Data\Microsoft\CLR Security Config\v2.0.*” folder
  • Delete “\Documents and Settings\YourProfileName\Application Data\Microsoft\DbgClr\8.0″ folder
  • Delete “\Documents and Settings\YourProfileName\Application Data\Microsoft\VisualStudio\8.0″ folder
  • Delete “\Documents and Settings\YourProfileName\Local Settings\Application Data\Microsoft\DbgClr\8.0″ folder
  • Delete “\Documents and Settings\YourProfileName\Local Settings\Application Data\Microsoft\VisualStudio\8.0″ folder
  • Delete “\Documents and Settings\YourProfileName\Local Settings\Application Data\Microsoft\VisualStudio\devices\8.0″ folder
  • Delete “\Windows\Microsoft.NET\Framework\v2.0.*” folder (assuming Windows is installed into \Windows\ folder)
  • Delete “\Program Files\Microsoft Visual Studio 8″ folder, ignoring any warnings you might get
  • Delete v2.0 assemblies from GAC by navigating to “\Windows\assembly” folder. v2.0 assemblies are the ones whose name start with System.*, Microsoft.* or vj* and have version of
  • Delete old Crystal Reports assemblies from GAC. Their names start with Crystal* and have version of 10.*

Reboot just in case, disable antivirus and antispyware software and you should be ready to install Visual Studio RTM.

Some helpful references:
Uninstalling Previous Versions of Visual Studio 2005.
Download Microsoft’s autouninstall tool.

Hope this helps.

Sergey @ USysWare

No Whidbey Beta 3 - thank God!

Thank God for that! I’m perfectionist myself but please, ship the darn thing. Hordes of developers out there, including myself, are dying to get their hands on RTM version. We don’t need any more delays!

According to cNet news:

“Through a feedback form on the Microsoft Developer Network Web site, developer customers asked Microsoft to release a third beta of Visual Studio 2005, which is due for completion on Nov. 7.

Representatives from Microsoft’s Visual Studio development group decided to pass on the suggestion. A few hours later, it posted a note saying, “We are confident that we will be able to ship you a high-quality product later this year.”

A company representative confirmed Monday that Microsoft is on track for a Nov. 7 delivery date.”

Sergey @ USysWare