The SocketWrench .NET class is designed for Visual Studio 2022 and earlier versions. SocketWrench provides full support for general purpose Internet programming and can be used to create both client server applications. Assemblies are provided for version 2.0 through 6.0 of the .NET Framework. Examples are provided for Visual Studio 2010 and later versions.
In this Microsoft marketplace you will find lots of different MS UI controls, as well as non-visual components, Microsoft utilities and Microsoft plug-ins to help you program in Microsoft Visual Basic, Visual C++ & Visual C#. You will also find Microsoft visual tools written by ISVs that can be used by MS Access developers or by MS Office programmers as Office components to be embedded inside their MS VBA or VSTO apps. There are also SharePoint tools and SharePoint Web Parts for MOSS bases apps being created by SharePoint developers. Plus for SQL Server you will find Microsoft utility products that allow you to access or bind to your data sources, compare data, manage your data, backup your data efficiently and much more. There are over 1,800 commercial products compatible with Microsoft software shown here in this Microsoft product gallery and many come with free downloads or free software trials for you to use listed in our Microsoft downloads product pages.
These are the steps I followed multiple times to get addins working in versions of visual studio other than 2010, using the 10.2.2 arcobjects sdk. My guess is this would probably work with 10.1 as well.
Like the BASIC programming language, Visual Basic was designed to have an easy learning curve. Programmers can create both simple and complex GUI applications. Programming in VB is a combination of visually arranging components or controls on a form, specifying attributes and actions for those components, and writing additional lines of code for more functionality. Since VB defines default attributes and actions for the components, a programmer can develop a simple program without writing much code. Programs built with earlier versions suffered performance problems, but faster computers and native code compilation has made this less of an issue. Though VB programs can be compiled into native code executables from version 5 on, they still require the presence of around 1 MB of runtime libraries. Core runtime libraries are included by default in Windows 2000 and later, but extended runtime components still have to be installed. Earlier versions of Windows (95/98/NT), require that the runtime libraries be distributed with the executable.
Visual Basic 1.0 was introduced in 1991. The drag and drop design for creating the user interface is derived from a prototype form generator developed by Alan Cooper and his company called Tripod. Microsoft contracted with Cooper and his associates to develop Tripod into a programmable form system for Windows 3.0, under the code name Ruby (no relation to the later Ruby programming language). Tripod did not include a programming language at all. Microsoft decided to combine Ruby with the Basic language to create Visual Basic. The Ruby interface generator provided the "visual" part of Visual Basic, and this was combined with the "EB" Embedded BASIC engine designed for Microsoft's abandoned "Omega" database system. Ruby also provided the ability to load dynamic link libraries containing additional controls (then called "gizmos"), which later became the VBX interface.
One additional MSM file to be aware of is CRRuntime_13_x_maps.msm. This MSM is required if your reports use the Crystal Reports mapping feature. For more information see the KBase 1529045 - CRVS2010 - How to create and distribute runtime for reports using MapInfo MapX?.
User Function Library (UFL) is dynamic link library (DLL), created by an application developer. As this is essentially "3rd party" DLL, it is not included in any merge module and thus it is up to the application developer to ensure that this custom dll is deployed and configured correctly on any client computer. Note that there are three types of UFLs, each with its own set of deployment and configuration requirements. The types of UFLs are C+, COM and .NET. C+ UFLs simply need to be installed into a directory where the application will be able to find it. The CRVS2010 bin directory is suggested (C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86). COM UFLs can be deployed to any directory, but must be registered using regsvr32.exe. VS .NET UFLs must be added to the Global Assembly Cache. For more information on VS .NET UFLs, see the blog Creating Crystal reports User Function Libraries (UFL) with Visual Studio .NET. 2b1af7f3a8