Here are the instructions to follow before you install Visual Studio 2008 RTM:

1. Go to the Control Panel and launch Add/Remove Programs
2. Remove all instances of Visual Studio 2008/Codename Orcas products
3. Remove any remaining supporting products in the specified order.
   • Remove “Crystal Reports for Visual Studio 2008 beta2″ (or “Crystal Reports 2007″)
   • Remove “MSDN Library for Visual Studio 2008 Beta”
   • Remove “Microsoft SQL Server Compact Edition 3.5″
   • Remove “Microsoft SQL Server Compact Edition 3.5 Design Tools”
   • Remove “Microsoft SQL Server Compact Edition 3.5 for Devices”
   • Remove “Microsoft Visual Studio Performance Collection Tools”
   • Remove “Windows Mobile 5.0 SDK R2 for Pocket PC”
   • Remove “Windows Mobile 5.0 SDK R2 for Smartphone”
   • Remove “Microsoft Visual Studio Web Authoring Component / Microsoft Web Designer Tools”
   • Remove “Microsoft Visual Studio Tools for Office Runtime 3.0″
   • Remove “Microsoft Device Emulator 3.0″
   • Remove “Microsoft Document Explorer 2008″
   • Remove “Microsoft Visual Studio Codename Orcas Remote Debugger”
   • Remove “Microsoft Visual Studio 64bit Prerequisites Beta” (64-bit platforms only)
   • Remove “Microsoft .NET Framework 3.5″
   • Remove “Microsoft .NET Compact Framework 3.5″

Now that you’re sure all the beta bits are are gone you can install the Visual Studio 2008 RTM edition of your choice…

Note that the list above are the products that were on my machine  and you might have additional products that require removal on your machine.

Update 20/11/2007:

ScottGu just published his own version of the list. When writing this post I started from the same list Scott has now made public but I updated it according to the products that were installed on my machine (removed some stuff, renamed some stuff to fit the name as it appears in beta2). So basically there shouldnt be a difference between the two…

Tags: .net, Visual Studio 2008

I’m currently uninstalling the beta bits from my machine in order to install the RTM version of Visual Studio 2008. My experience with this process on previous versions was pretty painful and so far with the 2008 versions I’ve had to re-image my machine in order to upgrade to beta 2.

So I hope this time the process won’t be as painful as it used to…

Update:
Update completed without any problem. Just be sure to follow these beta uninstall instructions.

Tags: .net, Microsoft, Visual Studio

The MSBuild Team Blog featured a series of posts about integrating MSBuild with Visual Studio.
Here is the summary of these posts:

• A New Series: MSBuild in Visual Studio
• MSBuild in Visual Studio Part 1: Loading and Saving Project Files
• MSBuild in Visual Studio Part 2: How the IDE Reads Properties
• MSBuild in Visual Studio Part 3: How the IDE Writes Properties
• MSBuild in Visual Studio Part 4: A Quiz on Project Escaping
• MSBuild in Visual Studio Part 5: Quiz Answers, Round 1
• MSBuild in Visual Studio Part 6: Quiz Answers, Round 2
• MSBuild in Visual Studio Part 7: Reading Items From the Project File
• MSBuild in Visual Studio Part 8: Writing Items To the Project File
• MSBuild in Visual Studio Part 9: Compiling at Design-Time Using the In-Process Compiler
• MSBuild in Visual Studio Part 10: What Does MSBuild Have To Do With Intellisense?
• MSBuild in Visual Studio Part 11: Other Special Targets
• MSBuild in Visual Studio Part 12: Compiling Inside Visual Studio
• MSBuild in Visual Studio Part 13: The Three Custom Loggers

Tags: .net, MSBuild, Visual Studio

Here are my answers to the second part of the questions (without using MSDNGoogleetc. except when noted):

Mid-Level .NET Developer

• Describe the difference between Interface-oriented, Object-oriented and Aspect-oriented programming.
  • Interface-oriented programming means defining and working strictly through interfaces.
    Object-oriented programming means defining defining a program using relationships between objects a classes (inheritance, polymorphism etc.)
    I’ve heard the buzz about AOP (aspect-oriented programming) but I have yet to study what exactly does it mean…
• Describe what an Interface is and how it’s different from a Class.
  • An interface defines a contract without implementation. A class implements an interface.
• What is Reflection?
  • Reflection is used to query .NET assemblies and types for information. It can also be used to create type instances, invoke methods and even emit .NET code at runtime (Reflection.Emit).
• What is the difference between XML Web Services using ASMX and .NET Remoting using SOAP?
  • I’ve never used .NET remoting but I assume the difference is that remoting is not as interoperable as web services.
• Are the type system represented by XmlSchema and the CLS isomorphic?
  • No.
• Conceptually, what is the difference between early-binding and late-binding?
  • When using early-binding the call information is known at compile time.
    When using late-binding the call information is only known at runtime.
• Is using Assembly.Load a static reference or dynamic reference?
  • Dynamic reference.
• When would using Assembly.LoadFrom or Assembly.LoadFile be appropriate?
  • For loading assemblies from given file or folder (such as plugins etc).
• What is an Asssembly Qualified Name? Is it a filename? How is it different?
  • The Assembly Qualified Name contains the assembly name, version and public key token and thus allows
    versioning and singing as opposed to a simple filename.
• Is this valid? Assembly.Load(”foo.dll”);
  • No because “foo.dll” is not an assembly qualified name.
• How is a strongly-named assembly different from one that isn’t strongly-named?
  • Strongly-named assemblies are signed using a privatepublic key pair which helps with code verification.
    signed assemblies could be placed in thee GAC.
• Can DateTimes be null?
  • No because it is a structure and not a class.
• What is the JIT? What is NGEN? What are limitations and benefits of each?
  • JIT means Just In Time compilation which means the code is being compiled just before it is supposed to run.
    This means longer startup time (because the code takes some time to compile) but more efficient compilation (since the compiler has more information about the target system etc.).
    NGen is used to pre-JIT code which yields faster startup time but the compiler produces less efficient code because it has less information.
• How does the generational garbage collector in the .NET CLR manage object lifetime? What is non-deterministic finalization?
  • It divides the objects into three generations.
    The first generation is used for short lived objects and is collected often (its cheap to collect it).
    The other two generations are used for longer term object.
    Non-deterministic finalization means that it is not known when the object’s finalizer is called since it is called when the GC decides to collect the object and not when the object falls out of scope etc.
• What is the difference between Finalize() and Dispose()?
  • Finalize() is called by the runtime (the GC) and Dispose() is called by the user.
• How is the using() pattern useful? What is IDisposable? How does it support deterministic finalization?
  • The using statement defines a scope at the end of which a given object will be disposed.
    Using the ‘using statement’ helps not to forget disposing of a disposable object.
    IDisposable is an interface used to define a way to dispose of objects in a deterministic manner.
    When the ‘using statement’ scope ends the Dispose() method is automatically called on the given object.
• What does this useful command line do? tasklist /m “mscor*”
  • It shows all the processes that loaded a DLL with a name matching the given pattern. In this case we will see all the processes using the .NET framework.
• What is the difference between in-proc and out-of-proc?
  • out-of-proc requires marshaling between two processes and thus slower.
• What technology enables out-of-proc communication in .NET?
  • Remoting.
• When you’re running a component within ASP.NET, what process is it running within on Windows XP? Windows 2000? Windows 2003?
  • The ASP.NET worker process.

Tags: .net, ASP.NET, Aspect-oriented programming, interview questions, Object-oriented programming, Scott Hanselman, web services, XML