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

Get Started with MongoDB Stitch : The New Backend As Service Offering from MongoDB

Halfway of this year, the guys from MongoDB launch their new backend as service product called MongoDB Stitch. While the launch is just for the beta, the promise of the service is quite interesting. MongoDB has been around for long now and some development stacks have been based on its database product, the MongoDB-ExpressJS-Angular-NodeJS (MEAN) and the MongoDB-ExpressJS-React-NodeJS (MERN) stacks to name a few. These stacks, however, relies on backend technology such as ExpressJS and NodeJS. The idea of provisioning servers and developing the backend solution makes it daunting for small to medium scale applications. MongoDB Atlas, at least made life much easier by providing on cloud database solution, but there must be a simpler solution, right? A solution the would stitch the backend and frontend together ( see what I did there ?).
MongoDB Stitch lets developers focus on building applications rather than on managing data manipulation code, service integration, or backend infrastruct…

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and Windows Workflow Foundation(WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time.

Why reinvent the wheel? So I started querying the internet for a better solution. I stumbled upon Stateless