Unfortunately I cannot help you much. The
Well, your options are really limited
Approach A
Move to .NET 4.0
Clearly A is associated with lot's of problems and require significant effort, while still being hacky. And the only advantage it gives you - "you are sticking with 9 years old obsolete framework". Though it might be exactly what is required in your case.
The B from other hand is a main stream officially recommended approach that requires almost no effort but does have a small price to pay - "your product will be running on a newer framework".
Only you can make this choice.
nbsbuilder was built with VS2010. I don't even have it any more and upgrading to VS2015 didn't work smoothly. The upgrade also introduces a dependency on a newer CRT (C-runtime) and this is what you would want to avoid.Well, your options are really limited
Approach A
- You can install VS2010.
- You can start fighting with C/C++ linking problems.
-
You can try to patch resources as I described previously.
Move to .NET 4.0
Clearly A is associated with lot's of problems and require significant effort, while still being hacky. And the only advantage it gives you - "you are sticking with 9 years old obsolete framework". Though it might be exactly what is required in your case.
The B from other hand is a main stream officially recommended approach that requires almost no effort but does have a small price to pay - "your product will be running on a newer framework".
Only you can make this choice.