Blue Ink was designed to work with Microsoft Visual Studio. Blue Ink's default set of templates output .sln and .proj files so you can immediately open and work with a generated solution using Microsoft Visual Studio. Yes, in most respects Blue Ink generated solutions are no different than manually coded solutions. Blue Ink generated solutions integrate fully with source control applications such as Microsoft SourceSafe either through Microsoft Visual Studio or externally.

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. See similar questions...

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... See similar questions...

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... See similar questions...

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. See similar questions...

No. QuickAdmin is a standard .NET control, so just needs to be referenced when compiling your C# code. See similar questions...

The source code distribution of sanos comes with project and solution files for Microsoft Visual Studio version 7. It can be compiled with Visual Studio version 6 by converting the project/solution project files in the build directory to version 6 project/workspace files. The prjconverter utility in the tools directory can be used for converting the project. This is a modified version of prjconverter by S. Rod. You can also use Microsoft VisualStudio .NET 2003 to build sanos. See similar questions...

Unfortunately not, since the Visual Studio Express Edition has a limited support for extensibility that does not match the tight integration needs of Mainsoft for Java EE. You need to install Visual Studio Standard or Professional Edition to use Mainsoft for Java EE. See similar questions...

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. See similar questions...

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 See similar questions...

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. See similar questions...

Before you begin, note that Cygwin is licensed under the GNU GPL (as indeed are all other Cygwin-based libraries). That means that if your code links against the cygwin dll (and if your program is calling functions from Cygwin, it must, as a matter of fact, be linked against it), you must apply the GPL to your source as well. Of course, this only matters if you plan to distribute your program in binary form. For more information, see http://gnu.org/licenses/gpl-faq.html. See similar questions...

While there is a growing set of commercial and open source tools for Java EE development, these tools are designed for Java?savvy developers. If you have invested a lot of time into becoming an expert in Visual Studio development, the .NET languages (C# or VB) and the .NET Framework (ASP.NET, ADO.NET, etc.), we believe Mainsoft for Java EE can be your most productive Java EE development tool. No. You can continue using Visual Studio to create Windows applications as you always have. See similar questions...

There are two main reasons. Speed and functionality. If your application needs to deliver real time mathematical results, you need speed. If your application needs to implement special, less known mathematical algorithms, not covered in standard math libraries, you need functionality. In either case MtxVec is a good choice. See similar questions...

in the command line box. There doesn’t appear to be a way to get clean to work with Visual Studio so the rebuild all switch is used here. The sed part of this command is used to parse the output from gcc and translate the error messages so Visual Studio understands them. If you have a makefile project already set up you can also set the make command line through the Project Settings dialog. See similar questions...

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... See similar questions...

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... See similar questions...

Wise for Visual Studio .NET is a specially designed Wise product that operates within the Visual Studio interface, with the full functionality of the Wise installation authoring environment. Wise for Visual Studio .NET™ is the only full-featured installation product embedded directly into Microsoft® Visual Studio® .NET. Our participation in the Visual Studio Integration Program and our close partnership with Microsoft gives us exclusive access to Microsoft technology. See similar questions...