|
Gary Wheeler wrote: Sorry for the Captain Obvious reply here
 The way I figure it, the engagement ring was a family heirloom passed down, maybe from mom or grandma.
Marc
|
|
|
|
|
I have VS 2015 installed as well, and no matter how I approach getting them to open in VS 2008 by double-clicking them from Windows Explorer, they will only open in VS 2015. VS 2008 doesn't even show up in the list of programs, and even selecting C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe doesn't work. The only way is to open them from inside VS 2008 through File > Open Project.
Anyone know how to correct this?
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
TNCaver wrote: Anyone know how to correct this?
get a horse?
Wrong message board.
Sin tack
the any key okay
|
|
|
|
|
Right-click on the sln file, select "Open With...", then VS2008.
Marc
|
|
|
|
|
VS 2008 doesn't show up as an option. If I click More Apps, it isn't there, either. If I then browse to devenv.exe in program files, it still opens in VS 2015.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
TNCaver wrote: VS 2008 doesn't show up as an option.
Yeah, sometimes that happens. Don't know why.
Marc
|
|
|
|
|
So far what MC said is true. So the reason's prolly due to a registry entry. That said, try searching in the registry for this VS2008 of which you say so much. Discrepancies can often be at fault or you might even be as bold as one who'd save the VS2015 slice (on_01.reg), substitute a logical VS2008 path/find/whatever in another slice then delete the VS2015 slice (off_01.reg) and try to start with VS2008.
Think of the Common Files idea. Many MS apps have shared drivers, etc.
Good luck.
|
|
|
|
|
This is a Windows Explorer configuration issue. Explorer can only associate each file type with a single application.
|
|
|
|
|
And Windows 10 will not let me change that association from 2015 to 2008.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
I don't have 2008 so cannot test that for you, but I can change its association to other applications.
|
|
|
|
|
If you do that, you will no longer be able to open solutions directly in VS 2015.
The problem is you can only have a single application registered to open files with any particular extension. In your case, that would be .SLN files. So, which one do you want? Open those in 2008 or 2015? The choice is up to you.
|
|
|
|
|
You should be able to use the Visual Studio Version Selector program to do this, I think.
Happiness will never come to those who fail to appreciate what they already have. -Anon
|
|
|
|
|
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! 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
