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.

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.

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...

Answer: Yes, as long as the application conform to logo requirements. Sometimes older runtime libraries violate security rules (es. Write access to WRP resources) or reliability rules (es. Fail APPVerifier checks). Migration to Framewark 2 is recommended but not required. In such cases, the ISV can contact swlogo@microsoft.com to work out solutions on a case by case basis. Answer: Certificates can be obtained from third party Certificate Authorities such as Verisign or Geotrust.

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.

Yes, but there are currently a few known issues that the development team are working on. DirectSound hardware acceleration no longer exists on Vista (resulting in broken support for 5.1/7.1 speakers); Skinned scrollbars may not be displayed correctly; Video playback may be a bit flaky (most likely related to old/buggy video drivers or directshow codecs) or doesn't work at all with Aero enabled; and DWM/Flip3D displays the built-in Classic skin for all Modern skins.

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.

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.

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

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

Yes, VBA exists in Office 2003 as it has in previous versions of Office. New XML functionality in Office Professional 2003 has been made available to developers through additions to the Office object model.

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.

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.

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.

CrypKey Instant has a feature that allows you to roll addtional dlls, files, and the CrypKey driver into the protected executable (Auto Append). While this feature is convenient to make a quick simple install of your program, this concept is not supported by Vista. For security reasons, Vista demands that regular use programs and installer programs be separated, as installer programs are treated differently.

Yes. You can use the Visual Studio Team Foundation Server MSSCCI Provider Beta 2, but be sure to disable strong name validation.

Yes. In order to do this you will need to buy Visual Studio Team Foundation Server and a Client Access License for proper communication with the server. Team Explorer, which is included with Team Foundation Server, is a stand alone client that uses the Visual Studio 2005 shell providing a UI for source control, work item tracking and all the other features. For more information on licensing Visual Studio Team System (including Team Foundation Server) see the Team System Licensing White Paper.

Assuming that you have successfully installed C-Sharpener For VB, the menu option should automatically appear. If it doesn't appear, then try the following: Turn on the checkbox to the left of C-Sharpener For VB and click the OK button. The menu option should now appear.

The Visual Studio Express Editions are an expansion of the Visual Studio and SQL Server product line to include fun, simple and easy-to-learn tools for non-professional developers like hobbyists, students and novice developers who want to build dynamic Windows applications, Web sites, and Web services.

Well, there is a compatibility problem. You can run a project from 2002 on 2003, but not visa versa. Once a 2002 is opened in 2003 it can't be opened in 2002. Of course, there are work-a-rounds but that beyond an intro class. Note: This class is about VB .NET 2003.

Framework 1.0 is not supported on windows Vista and Framework 1.0 assemblies may be run with Framework 1.1 runtime.

Answer: Many current and legacy products are supported including both Microsoft and 3rd Party products. Microsoft has put together a detailed list which you can access here. Answer: With Microsoft's commitment to Trustworthy Computing, many changes were made within the operating system. In fact, 350 changes that affected Exchange Server were made over the previous OS.

Visual Studio 6 support was removed in the October 2004 Update SDK. This does not mean you cannot use this SDK but there are no .dsw or .dsp files included in the SDK and there are some header file incompatibilities that require workarounds. Recommendation: if you're going to continue to use dshow, upgrade to VS.NET, otherwise download the DX 9.0b SDK if it's still available from Microsoft Downloads (see Links page).

Answer :Yes! VS.Net works with the .Net framework, while VS6.0 works with MFC or the Windows API directly, for the most part. They can be installed and run on the same machine without any considerations.

You need to use a second instance of Visual Studio to debug the one that's running the code. Put your control on a form. Start a second instance of Visual Studio and choose the Debug | Processes menu item. Double-click devenv.exe and choose Common...