Skip to main content

visual studio 2008

just last week our company already had the licensed copy of visual studio 2008, thats what you get being a MS gold partner. we have to use it right away to migrate some projects that we developed using the beta 2 release . the look and feel did npt change a bit but i bet there are a lot of changes that are waiting to be discovered.

one of the most notable changes was on VSTO (Visual Studio Tools for Office). VSTO has been around since VS2005 and we had no problem migrating it to beta 2 of VS2008. well things have changed and there are new features in 2008 plus changes in assembly names. so here are the things that we got and the workarounds that we made :




The following assemblies are no longer supported in VS 2008 Release. Remove it from the reference list.
Microsoft.VisualStudio.Tools.Applications.AddInBase.dll
Microsoft.VisualStudio.Tools.Applications.Common.dll
Microsoft.VisualStudio.Tools.Office.dll
Microsoft.VisualStudio.Tools.Office.Common.dll

Replace above with the following assemblies
Microsoft.VisualStudio.Tools.Applications.Runtime.v9.0.dll
Microsoft.VisualStudio.Tools.Office.Runtime.v9.0.dll
Microsoft.Office.Tools.v9.0.dll
Microsoft.Office.Tools.Common.v9.0.dll

In Ribbons ExcelRibbon, WordRibbon, etc.. is replaced by one object which is OfficeRibbon. In your ribbon class you need to change the base class from XXXXRibbon to OfficeRibbon (see snippet below). Then open the ribbon and change the RibbonType property to any office solutions you wish your ribbon to support …

SNIPPET

Old:
public partial class MyRibbon : WordRibbon
{
…..
}

New:

public partial class MyRibbon : OfficeRibbon
{
….
}




feel free to comment on this and add new changes that you may have run into.

Comments

Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :

"**/*.pyc":{"when":"$(basename).py"},"**/__pycache__":true

renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!



I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

Automatic Properties and Object Initializers in .Net 3.5

With the release of .Net 3.5 alongside with Visual Studio 2008 , new enhancements was again introduced . Some maybe well pronounced such as the inclusion of WCF, WPF , LINQ in .Net 3.0 and some just came unnoticed. If you have been accustomed of using a particular method or technique in implementing a certain code in .Net 2.0 , because of backward compatibility , you may not even notice that there are new ways of implementing it in .Net 3.5.

Here are two new concepts in .Net 3.5 that a developer may not notice ( at least in my opinion ) : Automatic Properties and Object Initializers . To illustrate these two , I am going to present the pre-.Net 3.5 way (.Net 2.0) and the .Net 3.5 way in creating a simple class with simple properties.

Automatic Properties

Creating a class can be tedious , especially when working with a list of properties , . One way to get around having to type the code for a private field and its public property getter and setter is to use a refactoring tool. However, …