Creators of VS 2005, you're doing a heck of a job!
-
it's a feature. You should try and drop a solution file instead. It works.
Oh, right - that makes it better. So can i expect VS2008 to introduce even more such "features"? How 'bout not accepting dropped .cpp files either - i know i always wanted to have to open a solution to view those. Or maybe they can introduce some crazy new "metasolution" that wraps up multiple solutions, and only allow those to be dropped... :rolleyes:
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
-
Oh, right - that makes it better. So can i expect VS2008 to introduce even more such "features"? How 'bout not accepting dropped .cpp files either - i know i always wanted to have to open a solution to view those. Or maybe they can introduce some crazy new "metasolution" that wraps up multiple solutions, and only allow those to be dropped... :rolleyes:
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
Be careful Mr Shog9. Ask and ye shall receive... ;P
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
When you drag and drop the project file onto the VS.NET (2002,2003 and now 2005), you get a message: Project files cannot be dropped onto Visual Studio. They must be opened via the File menu. Does anybody else think this is stupid? Why giving me a shitty message box instead of just opening the darn file? WTF!?
What would you like it to do? Open the project in a new blank solution, thereby closing the current one? Add the project to the current solution? If you implement either one, you'll frustrate half the community who expects it to do the other. The solution is to frustrate everyone :)
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
What would you like it to do? Open the project in a new blank solution, thereby closing the current one? Add the project to the current solution? If you implement either one, you'll frustrate half the community who expects it to do the other. The solution is to frustrate everyone :)
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
Well, i would be happy with the later (assuming there is actually a solution open). But if they were really interested in not pissing off those poor souls who suffer through life without my work habits, then a message box asking which behavior was desired would still be less annoying than a message box bluntly refusing to do anything.
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
-
Well, i would be happy with the later (assuming there is actually a solution open). But if they were really interested in not pissing off those poor souls who suffer through life without my work habits, then a message box asking which behavior was desired would still be less annoying than a message box bluntly refusing to do anything.
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
I agree. Especially if you could default the message box choice in the options somewhere.
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
When you drag and drop the project file onto the VS.NET (2002,2003 and now 2005), you get a message: Project files cannot be dropped onto Visual Studio. They must be opened via the File menu. Does anybody else think this is stupid? Why giving me a shitty message box instead of just opening the darn file? WTF!?
"A document with the name 'foo.xls' is already open. You cannot open two documents with the same name, even if the documents are in different folders." First, why the utterly retarded limitation, second, the documents have the same name, how the hell can they not be in different folders.
"Time sneaks up on you like a windshield on a bug."
- John Lithgow -
pc128 wrote:
Does anybody else think this is stupid?
Yes. In fact, while i've had VS crash on me, lock up on me, chew up massive amounts of memory and then lose project files, none of those bug me as much as that one, stupid, error message. It represents everything that was unnecessarily broken in the move from VS6 to VS2k1, and that is why my ultimate goal as a programmer now is to reach a position where i can find myself in a small, locked, windowless room with a lighter, a large cigar, and the person responsible for that error message. :|
---- Scripts i've known... CPhog 0.9.9 - make CP better. Forum Bookmark 0.2.5 - bookmark forum posts on Pensieve Print forum 0.1.1 - printer-friendly forums
Shog9 wrote:
my ultimate goal as a programmer now is to reach a position where i can find myself in a small, locked, windowless room with a lighter, a large cigar, and the person responsible for that error message.
A large, heavy stick might be handy to have on such an occasion, too. Just in case you run out of cigar before you're done doing the Lord's business. "...a photo album is like Life, but flat and stuck to pages." - Shog9
-
"A document with the name 'foo.xls' is already open. You cannot open two documents with the same name, even if the documents are in different folders." First, why the utterly retarded limitation, second, the documents have the same name, how the hell can they not be in different folders.
"Time sneaks up on you like a windshield on a bug."
- John LithgowBruce Duncan wrote:
why the utterly retarded limitation
VBA.
workbook = Application.Workbooks["Book1.xls"]- The VBA calls don't refer to paths - just the file name.Bruce Duncan wrote:
the documents have the same name, how the hell can they not be in different folders.
I'm stumped :)
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
it's a feature. You should try and drop a solution file instead. It works.
You can open a project file from the menu without a solution, so why not drag and drop? Jeremy Falcon
-
it's a feature. You should try and drop a solution file instead. It works.
Igor Vigdorchik wrote:
It's not a bug, it's a feature
:laugh: Right said! ;P
-
"A document with the name 'foo.xls' is already open. You cannot open two documents with the same name, even if the documents are in different folders." First, why the utterly retarded limitation, second, the documents have the same name, how the hell can they not be in different folders.
"Time sneaks up on you like a windshield on a bug."
- John Lithgow:-D Good one! I should use excel more, i didn't think it could be so funny!!!
-
What would you like it to do? Open the project in a new blank solution, thereby closing the current one? Add the project to the current solution? If you implement either one, you'll frustrate half the community who expects it to do the other. The solution is to frustrate everyone :)
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
If I drag it into the editor, I wanna edit it, if I drag it into the solution explorer I wanna open it. Isnt rocket science :)
-
When you drag and drop the project file onto the VS.NET (2002,2003 and now 2005), you get a message: Project files cannot be dropped onto Visual Studio. They must be opened via the File menu. Does anybody else think this is stupid? Why giving me a shitty message box instead of just opening the darn file? WTF!?
-
Bruce Duncan wrote:
why the utterly retarded limitation
VBA.
workbook = Application.Workbooks["Book1.xls"]- The VBA calls don't refer to paths - just the file name.Bruce Duncan wrote:
the documents have the same name, how the hell can they not be in different folders.
I'm stumped :)
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
Ryan Binns wrote:
VBA. workbook = Application.Workbooks["Book1.xls"] - The VBA calls don't refer to paths - just the file name.
For real? :doh: How come Word doesn't suffer from the same limitation then?
"Time sneaks up on you like a windshield on a bug."
- John Lithgow -
Ryan Binns wrote:
VBA. workbook = Application.Workbooks["Book1.xls"] - The VBA calls don't refer to paths - just the file name.
For real? :doh: How come Word doesn't suffer from the same limitation then?
"Time sneaks up on you like a windshield on a bug."
- John LithgowBruce Duncan wrote:
For real?
I believe so, but then again I may be leading you up the garden path - perhaps the VBA limitation is because of the Excel limitation, not the other way around. Either way, they're both the same.
Bruce Duncan wrote:
How come Word doesn't suffer from the same limitation then?
No idea. I assume it's because they were created by different development teams and the Word team had a better design process ;)
Ryan
"Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
-
"A document with the name 'foo.xls' is already open. You cannot open two documents with the same name, even if the documents are in different folders." First, why the utterly retarded limitation, second, the documents have the same name, how the hell can they not be in different folders.
"Time sneaks up on you like a windshield on a bug."
- John LithgowI didn't even know about that idiocy until eight months ago when my then CTO suggested it as a great solution to a problem we were facing. (Once again it shows that just because someone does something brilliant once, doesn't mean he should be making project-wide, let alone business decisions.) Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke