|
What used to work for me when push came to shove was just deleting the solution file after you write down all the files in the project that get referenced there and reassembling them in an updated 2015 project.
If that doesn't work, and trying to get a MS wizard to chime in hasn't yet resulted in a conversion of some kind, you could try to search MSDN for a possible workaround.
|
|
|
|
|
The problem is that you installed VS2008, then installed VS2015 after it.
To get the behavior that you want, install VS2008 after VS2015.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
You could write to Chris Maunder. He's been specializing on Win10 & Visual studio issues lately. Hehe 
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy Falcon.
|
|
|
|
|
VS2015 and later are pretty assertive about their claims of letting you do 'down-version' development. Supposedly when you open VS2008 and later solutions/projects, they retain existing settings.
That said, I have the following installed on my dev box running Win7:
Visual Studio .NET 2003 (don't ask)
Visual Studio 2005
Visual Studio 2008 SP1
Visual Studio 2015
and they were installed in that order. I can double-click on .sln files in Explorer and the open in the proper version of Visual Studio: 2003, 2005, 2008, or 2015.
Software Zen: delete this;
|
|
|
|
|
I think I've come up with a viable and reasonable configurable Excel worksheet importer for my SQL Express Agent project. Hell, it might even deserve its own article.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
|
Excel interop?
Just been there (but I was mostly doing export - only had to read template & reporoduce - a lot easier than straight import.)
And then it was outlook - just finished (quick and dirty outlook util),
to cap it off possibly some word is next.
fun all around!
... really thinking about taking a few weeks holiday (even before #3).
Sin tack
the any key okay
|
|
|
|
|
Nope - not using Office Interop for it. That would have taken me far longer, and would have made it a fragile house of cards.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
not that fragile if done carefully, but fully agree it's definitely a challenge
(and the slowness is not just the dev, interop runs like a pig on rollerskates on ice, and then there's the challenge if the user is in that office app at the same time.)
Sin tack
the any key okay
|
|
|
|
|
I'm using ExcelDataReader (NuGet package) to load the data into a DataTable, and then doing all the mechanical stuff myself. Including the code that handles database queries and copious comments, it's less than 900 lines of code.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: NuGet package
PTUI.
|
|
|
|
|
Without comments and blank lines (but still formatted), it's less than 500 lines. 
The larger the file, the longer it takes, but it's still much faster than using interop.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 17-Aug-17 13:59pm.
|
|
|
|
|
We've given up on trying to import Excel (via SSIS). The final nail in its coffin was that the Data Center folk said that we couldn't even put the Standalone ACE Engine on our servers -- "Oh no! That's MS Office! You can't put that on a server!"  . So now we do CSV instead.
How well does yours handle IPv4 addresses? I continually see SSIS importing them as floating-point values! 
|
|
|
|
|
Hmmm, it never occurred to me to try that. Lemme check real quick.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
string - BOO-YA! The caveat is that the column contain at least one value that cannot otherwise be interpreted as a double of course).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Yes, and everyone but MS knows that you can't interpret an IPv4 address as a double.
|
|
|
|
|
My importer tries to determine the most appropriate data type for the column, the ultimate fallback type is string. If you have 100 rows of data, and the first 99 are doubles, but the last is an IP address (for instance), it will report the data type for that column as a string.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 17-Aug-17 13:32pm.
|
|
|
|
|
Sure, but then why would MS choke on a list containing all IPv4 addresses (nothing that looks like a double except to them). 
|
|
|
|
|
If you want, I can get a zip file together with some instructions for use, and email it to you to try out.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Have a look at NPOI
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
"Found conflicts between different versions of the same dependent assembly that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed."
Either they aren't actually listed or they are buried so deep as to be invisible.
To the devs who wrote this pointlessness: If you can see there's a conflict why not list it then and there?
What about:
"Found conflicts between different versions of the same dependent assembly "Assembly.dll (1.2.3.4)" and "Assembly.dll (1.2.3.5)" that could not be resolved."
There - was that hard?
cheers
Chris Maunder
|
|
|
|
|
You are asking Microsoft to be user friendly?
I knew you were a glass half full person!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Been there. I was upgrading a project to newer versions of .NET Framework, ASP .NET MVC and the cascade of packages that needed to be updated when I ran into this. It is quite a manual task to figure out where the problems are and how to solve them.
The promise of freeing us from DLL hell, well, I am still waiting for that to be fulfilled.
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
seriously, what's the point of upgrading target in an existing development (unless still very fresh)? If a mature project is happy in say 4.0 it really should be left there and NOT pushed to the new target.
1. avoid these issues
2. keeps installation simple - if got multiple proj's in a solution some not updated then have to install the multiple .net's on older machines
3. it's not as if ms fix anything - they just add more [mostly bloat - even then even older versions can achieve identical results perhaps albeit with a few more lines of code].
And really for the sake of "compatibility" often they can't or shouldn't ever fix some of the "mysterious"/"expected" issues/behaviours... many of their own apps would break if they did that.
Yes [nearly all] exception causing bugs can be fixed, but operating behaviours even if they seem wrong or non standard must never be changed
... imagine if they decided next version of .net would zero base VB arrays (and all the dumb-ass newbie devs quickly open VS and flick projects to the new target?)
In short:
- minimally a waste of time, but in fact
- a very bad practice.
Sin tack
the any key okay
|
|
|
|
|
It was not a mature project. The project was shelved years before and it was decided to dig it up and restart the effort. It is as simple as that.
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
