Hi.
I have been trying to get in to VS development for a while. I am a VB Classic programmer from way back to Version 1.
During my older programming days we had what was known as DLL Hell - where different versions of DLL's would conflict and cause issues.
Nowadays I am getting stuck on Framework hell. It's really an issue for me as every time I start to try and get into VSxxxx development I end up having to bring in professional help.
For example - we use MySQL and Devart's DotNet Connector software.
So - using VS2003 I develop an application and install it.. and it works. It was my first app so the code was crappy.
Several years later I need to make some changes. I use VS2010 and the current DotNet Connector. All hell breaks out. Framework errors and cryptic messages. I have to being in a local expert to work out the framework issues.
More mods with VS2012 and again all hell breaks loose.
I am now contemplating going to VS2015. We still have a legacy server with Win 2003 on it. It still has software that needs to be maintained. I cannot continue to bring 'experts' in to fix the framework issues.
One it costs, secondly I am the IT expert in my company and it looks very bad on me.
Any suggestions on how to handle the VS migrations with better grace than contemplating re-writing the app from scratch every time I need to make a change.
Yes ASP.Net v5 looks WONDERFUL. Though I bet that if you try and run it on a Win 2003 you will be told to get a new server/wrong frameworks etc. Small companies like ours cannot dance to the whim of the market and upgrade every year to the latest and best
servers etc.
Many thanks for any suggestions. I want to move a way from vb Classic but it's the only thing I have that will reliably run on ALL platforms!!!
Dave
