FreeTexBox in Visual Studio 2010 - visual-studio-2010

I've downloaded and using FreeTextBox control in visual studio 2010 (.Net Framework 4.0)
but i got the following error.

You might try to run depends on its dll to see if needs other dlls that can not be found (might be some vcredist dll).

Related

How do I build a Visual Studio Extension (VSIX) that targets Visual Studio 2010-2017

Our build environment is VS 2015 (ideally) targeting .net 4.0
We have just re-worked our visual studio plugins based on the Visual Studio extensibility project template in VS 2015. The resulting VSIX works great on VS 2015 & 2017 RC1.
However I would like to target the VSIX at VS 2010 (and ideally 2012). This is where the problems start....
VS 2010 uses .net 4.0.
I drop the compiler to .net 4.0
The VS 2015 (4.5) assemblies wont load (i.e. Microsoft.VisualStudio.Shell.14.0).
Thats OK as I don't use anything in them, so I drop the references to them in favour of the version 10.0 (2010) ones.
Great the code compiles.
But the VSIX package does not
1>C:\Program Files
(x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5):
warning MSB3274: The primary reference
"Microsoft.VisualStudio.Imaging, Version=14.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL" could not
be resolved because it was built against the
".NETFramework,Version=v4.5" framework. This is a higher version than
the currently targeted framework ".NETFramework,Version=v4.0".
So the problem seems to be that if I target VS 2010 I need it to build as .net 4.0, but the VS 2015 build script requires .net 4.5.
I'm wondering if its possible to use the VS 2010 build tools in a VS 2015 project? Or must I convert my VS 2015 project back to VS 2010?
UPDATE
Starting to think this is not possible for other reasons...
https://learn.microsoft.com/en-us/visualstudio/extensibility/faq-2017
The new VSIX v3 format is backward compatible with VSIX v2, so you’ll
still be able to have a single VSIX with a single VSIX ID that
supports Visual Studio 2012 and later. The new VSIX v3 format does not
support Visual 2010 and earlier. To support Visual Studio 2010 onward,
you will need to create a separate extension (with a separate VSIX
ID).
I have ran into similar problem, so I have created a Nuget package called VsixUpdater, which can do the VSIX migration automatically if added to a VSIX project, it even works with older versions of Visual Studio (I tested it with 2012), after adding the package the generated VSIX packages will be V3 and 2017 compatible, see https://github.com/axodox/VsixUpdater for details.
Create a seperate project and VSIX for VS 2010 and another for VS 2012 and later. You can have a look at my source here: https://github.com/ErikEJ/SqlCeToolbox
Notice that I require .NET 4.5.1 for my VS 2010 extension also (simply requires that .NET 4.5.1 is present/installed on the PC, and it is built in to Windows 8.1 and later)
In the end I ended up with 2 projects
A project targeting VS 2010 compiled under .Net 4.0 using a version 2.0 manifest (built using VS 2015).
A project targeting VS 2012 + compiled under .Net 4.5
using a version 3.0 manifest (built using VS 2015).
There has been a certain amount of faffing around with references, but it all seems to work. Our only outstanding issue is the code signing, as VS 2015 will not accept anything below SHA256 and VS 2012 will not accept SHA256....

VSIX visual studio 2010 compatible

I am trying to extend some functionality using VSIX.
When I double click on the VSIX installer it, the following screen pops up. Visual studio 2013 is the only option it provides. But we use Visual studio 2010 for our development.
Can something suggest how to modify the manifest file and steps to make this VSIX 2010 compatible?
Thank you
No, you will most likely have to get the source code of the existing extension, and then build a new one for vs 2010 using the 2010 sdk
As ErikEJ already said, you need to use VSIX Manifest Version 1.
I did it using the instructions here. There is documentation of VSIX Manifest Version 1 here.
You must target Framework Version 4, but there is no need to build with Visual Studio 2010.

how to make standalone visual studio application which can run on any system without having visual studio

I made an application using VS 2010 and want to run that application on other system which don't have VS 2010.
How can i make my app independent of dependency from VS 2010,so that it can run on any system without installing VS 2010.
If this is a managed application then you need only the appropriate .NET framework version on the target machine (and of course any other dependencies your app may have).
If this is a native application then you need the VC++ 2010 Redistributable package. You need however the redistributable that matches your VS 2010 version (RTM or with SP1) and the project target architecture (x86, x86, IA64). Here are the links for the VC++ 2010 redistributables:
x86
VS 2010 RTM
VS 2010 with SP1
x64
VS 2010 RTM
VS 2010 with SP1
IA64
VS 2010 RTM
VS 2010 with SP1
You need to create an installer for it. The installer will install the .NET framework and any other requirements you may have.
I googled 'creating installer in visual studio 2010' and got some encouraging results.
Examples from results:
https://www.youtube.com/watch?v=IEgE51Lcpg0
http://msdn.microsoft.com/en-us/library/t71a733d.aspx
http://msdn.microsoft.com/en-us/library/ee942965%28v=vs.100%29.aspx
Search for ClickOnce in case the application needs to run for noon Admin users (installs to local user folders).

Visual Studio 2008 and Visual studio 2005

I am developing a Windows Application using the .net Framework 2.0 and Visual C#(Microsoft Visual Studio 2008) in my PC.
On the completion of my project I have to execute it in a system which has Visual Studio 2005 and .net framework 2.0.
So my doubt is if I develop an application in Microsoft Visual Studio 2008 will I be able to execute it in Visual Studio 2005 properly? Is it possible?
Please help me!
Thanks in advance!
The project files are compatible between the two IDEs, but the solution files are not. You may be able to execute it in VS2005 if you create a new solution in 2005 and add the projects to the new solution.
http://blogs.msdn.com/djpark/archive/2007/11/07/how-to-use-solutions-and-projects-between-visual-studio-2005-and-2008.aspx
Create the project in Visual Studio 2005
Save a copy of it somewhere
Upgrade to Visual Studio 2008, do your development work.
Drop your finished project back into your original Visual Studio 2005 project and compile
There should be minimal differences in the code so long as you don't use any .NET 3.5 features.
Note: So long as you use .NET 2.0 features only, the project will run just fine on the Visual Studio 2005 machine
It depends on what you mean by 'execute'. You can run your application just fine on your target machine, that has nothing to do with Visual Studio. As long as the framework version is the same (or higher) you should have no problems.
However, if you want to open your solution in Visual Studio 2005 while it was built using 2008, you will run into problems, as they are not backwards compatible.
Replace Version 10.0 in *.sln files with Version 9.00
Replace 2008 with 2005 in *.sln
Replace Version="9.00" with Version="8.00" in each *.vcproj file

Is there a way to change .NET framework version of Visual Studio 2005 to 3.5?

Is there a way to change .NET framework version of Visual Studio 2005 to 3.5?
No. Visual Studio 2005 only supports .NET 2.0 out-of-the-box. It can be updated to support .NET 3.0.
It is possible to compile .NET 3.5 code with a Visual Studio 2008 Express Edition, or without Visual Studio 2008 using Mono and I think the Windows/.NET SDK. However these will obviously not be integrated into Visual Studio 2005.
Visual Studio 2005 only supports .NET 2.0. The format of the solution file (.sln) changed in Visual Studio 2008 to allow you to select the target .NET version.
VS2008/2010 have a visual way of setting the project setting "TargetFrameworkVersion" which makes it easier, however I have found that adding the same tag to a VS2005 project will change the target framework. You might try adding 1(one) of the following into the section of your VS C# project.
<TargetFrameworkVersion>v3.0</TargetFrameworkVersion>
<TargetFrameworkVersion>v3.5</TargetFrameworkVersion>
<TargetFrameworkVersion>v4.0</TargetFrameworkVersion>

Resources