Yes the product id you received when you purchased the license for Ref++ VS2003 can be used to activate the version of Ref++ for VS2005.

In VS2003, debug info for unmanaged code is turned off by default. This is why you will not see the call stack including code in the System DLLs. To enable debugging for unmanaged code go to your project properties dialog and turn on as shown here: Contributed...

The MSDN Library for Visual Studio 2005 provides access to legacy documentation via the MSDN Online search provider, accessible from the Search page. Access to legacy documentation is also available on earlier editions of the MSDN Library installed on your computer.

You will need to download and install additional components. Please see the Visual Studio Developer Center for more information. No, each release of Visual Studio is tied to a specific version of the .NET Framework. The Express Editions can only be used to create applications that run on the .NET Framework 2.0.

It's here: http://msdn2.microsoft.com/library/default.aspx The documentation system previews some new design ideas and new URL model as described here . MSDN welcomes your feedback on the new system at that page.

Once your payment has been accepted you will be sent an email within 24 hours containing the product id to activate your Ref++ installations.

Yes. Associated courses require MCTs to hold a credential to teach them. These requirements must be fulfilled approximately 90 days after the availability of each Professional Series credential. The MCT Program Competencies Web site provides course-specific requirements and deadlines for attaining new competencies. You will not be authorized to deliver courses that require the new certifications.

Generally speaking, yes. Please note that there have been some API changes between the betas and the official release, so you may have to make some updates to your code accordingly.

VC 8 compatibility is not complete in the Windows 2003 SP1 Platform SDK from Microsoft. There are guidelines for fixing the issues in Mike Wasson's blog. There are Vista Windows (Platform) SDKs available to MSDN subscribers. These provide updated headers. Note that the naming of the PSDKs is confusing: the name is the most recent Windows version supported but earlier versions are also supported. See the release notes for a particular PSDK for details.

Microsoft Visual Studio 2005 solution runner is built on MSBuild runner, which is discussed upper. Differences are in TeamCity Administration Web UI only. You may configure this runner to run NUnit tests.

To see the help topics within Visual Studio 2005 and Visual Web Developer 2005, go to Tools > Options. Under Environment > Help > Online (make sure "Show all settings" is checked), ensure that "Try local first" is selected. This will find the installed help files before attempting to look online. I love these Controls! They've allowed me to create a web-application that I couldn't even dream of doing without them...my boss now thinks I'm a genius!

It is possible using Spices.VSIP.Obfuscator - it includes Visual Studio Integration Pack and MsBuild Integration. With this tool you can use VSIP features of Spices.Obfuscator, or add tasks using MSBuild integration into Visual Studio 2005 projects or MSBuild scenarios.

No. Unlike SSRS 2000, which required users to purchase Visual Studio 2003, SQL Server 2005 comes with Business Intelligence Development Studio, which provides the Visual Studio shell and the business intelligence projects including Report Designer and Report Builder Model Designer. If users already have Visual Studio 2005, these projects are installed along with language projects.

Assuming that you have successfully installed Fast Formatter and you have any edition (except the Express edition) of Visual Studio .NET 2005 installed, the menu option should automatically appear as described in the tutorial. If it doesn't appear, then please try the following: Turn on the checkbox to the left of Fast Formatter and click the OK button. The menu option should now appear.

Technically speaking MIIS does not require Visual Studio at all, but it is a very good development tool choice for developing MIIS 2003 rules extensions. The minimum requirements to compile rules extensions are the .NET compilers available for free in the .NET Framework SDK at http://msdn.microsoft.com. Top For MIIS 2003 to work in a warm standby configuration, Active Directory is required. See the technical overview for MIIS 2003 Planning for High Availability at http://microsoft.

No. Rules extensions can be built and compiled on a separate computer, then copied to the extensions folder on the MIIS server. Installing the debugger on the MIIS computer is a good idea, since it will improve the troubleshooting experience. Top

Microsoft Visual Studio .NET 2003 solution build runner is build on the base of NAnt runner, described before. Solution task is used to run the build. Projects files are expected to be wellformed XML. You may configure this runner to run NUnit tests.

Answer: Changes in Windows vista impact Visual Studio so that Microsoft is unable to provide support for Visual Studio .NET 2002 or Visual Studio .NET 2003 on Windows Vista. see Visual Studio on Windows Vista for additional information.

See the article A Utility to Convert VS.NET 2003 Project Files on The Code Project . Contributed from George Shepherd's Windows Forms FAQ

Use the Microsoft Visual Studio 2005 newsgroups which you can use through the web interface or follow the directions on that that page for using an NNTP reader. For Windows Forms support, see the Forums In addition, there are a number of free and for...

Open Visual Studio and create a blank solution file (File>New Project>Other Project Types>Visual Studio Solutions>Blank Solution) Browse to the place you just created and then in the Location textbox add a new subdirectory name onto the end of the path Every time you open your ASP project you MUST use the Open Project command to browse to the .sln file you created instead of using the Open Website command.

Use our Mono Migration Analysis tool to check if everything that your application uses has been implemented in Mono or if there are special considerations to keep in mind. The Mono API today is somewhere in between .NET 1.1 and .NET 2.0, see our Roadmap for details about what is implemented.

The service has been tested with a C# client auto-generated from WSDL by the wsdl.exe tool. It should work fine from any .NET language.

I have code snippets that I use often. How can I manage them so I can easily used them? In Visual Studio, you can store commonly used code snippets on a tab (other than the Clipboard ring) in your Toolbox. You use drag and drop techniques to move the...

Use the ToolboxItem attribute set to false on your component or control class. This will prevent it from appearing in the Toolbox. [ ToolboxItem( false ) ] public class MyComponent : Component{..} Contributed from George Shepherd's Windows Forms FAQ

No. While Visual Studio makes deploying "ClickOnce" applications simple, there are several other ways to deploy "ClickOnce" applications. The .NET Framework SDK includes a tool named MAGE(Manifest Editor & Generator) that provides both a UI (mageui...

I recommend a fast computer with lots of hard disk space and lots of memory. Note that if you want to run all the features of VB .NET you need to have Windows 2000 Professional or Windows XP Professional.