|
The Menu designer is found in Microsoft.VisualStudio.dll, unfortunately its a private class so you can't access it normally.
James
Simplicity Rules!
|
|
|
|
|
I am trying to install VS .Net on Windows 2000 Professional. It asks me to run the Windows Component Update. When I do this it seems to take forever. Almost appears that it is frozen. Is it supposed to take so long or has something gone wrong. It has been over an hour for me now.
Thanks
|
|
|
|
|
Welcome to hell. Did you have the beta installed before hand ? I had to do a full uninstall of the beta, AND any add ins I had running, and in the end I found that the only way to make the install work at the end ( which you're still a long way short of ) was to bring up the task manager and kill tasks until it completed.
Installation took me 8 hours +, on W2000 Pro.
Christian
The tragedy of cyberspace - that so much can travel so far, and yet mean so little.
"But there isn't a whole lot out there that pisses me off more than someone leaving my code looking like they leaned on the keyboard and prayed that it would compile.
- Jamie Hale, 17/4/2002
|
|
|
|
|
Installing VS .NET takes a long time. Don't immediately jump to the conclusion that it has hung. It took me one and a half hours, and I have a good CD-ROM (24x), a fast HD (ATA-100), and a fast processor. (And that was the professional version that I installed, I can only guess how long the more expensive versions take.)
|
|
|
|
|
Well I am still stuck at simply installing the Windows Component Update. I did learn that the install has to be killed after some time ( by luck and later by a response to my query).
I managed to install two parts of the windows components update. Now an stuck with a) Setup Runtime Files and b)Microsoft .Net Framework.
Also this is a clean install. Brand new ghard drive. With a new installation of Win2K Pro and SP2.
Now at 4 hours where the progress bar is complete but it will not move to the next component.
Will reboot and then post an update.
Thanks
|
|
|
|
|
This is driving me nutsssssssssssssss. Now my IIS will not start in Win2k. Right now I wish I could go back to DOS. 
Now when I boot my computer FTP and WWW services just will not start. .Net is still not installed. I cant even uninstall IIS because win2k installation first tries to shut it down which it cannot because it is still trying to start the bloody thing.
Am I the only one having to live through this? Any ideas?
Thanks.
|
|
|
|
|
I installed mine just last night on Win2K Pro as well. Same problem. I had noticed that even though Norton Antivirus was deactivated before the install, it was starting up mid install and things would freeze. I finally uninstalled all of my norton products and it went better. After getting past the components part, it did apear to lock once. While I was waiting I tried to browse the web and notice the IE was also frozen. I therefore stopped explorer and restarted it and from then on the installation went fine.
Hope this helps.
Paul
|
|
|
|
|
I don't want to use default location in VS.NET. How can i change location for each ASP.NET project? Thanks! 
|
|
|
|
|
I think you can create a virtual directory before hand (named after your project) then you can create your project which would put the files there.
James
Simplicity Rules!
|
|
|
|
|
I don't want to use default location in VS.NET. How can i change location for each ASP.NET project? Thanks!
|
|
|
|
|
Can anyone provide an conclusive answer on .NET's role in process control. One of the big selling points for .NET is the 'Services' concept. This is (if I am not mistaken [please correct me if I am wrong]) a stateless environment. A example of a Web Service often given is the 'Ticket purchase'. That example works great; I provide the information, marshal it along with the method request and I get a response. But what if i want to make a request like, Purchase tickets, but only when they fall below this point, and notify me when the purchase is made. Just wonder'n....
Russ Danner
rdanner@neural-renaissance.com
|
|
|
|
|
I have some troubles with making Add-In for VS.NET.
I need to receive Event about saving document and Build complete.
Can you have me with any information ? MSDN page, source or any other...
( Add-in in C++ )
Thank you.
Pavel Sokolov,
CEZEO software,
LanTalk Network,
http://www.cezeo.com
http://www.lantalk.net
|
|
|
|
|
Having just purchased VS .NET, I am wondering whether .NET apps will run on the Win9x/ME series of OS's - i.e. have MS actually released any .NET run-times for Win9x/ME?
Cheers,
Free
|
|
|
|
|
Whoops, sorry guys - just noticed the answer to this further down in the forum.
Cheers,
Free
|
|
|
|
|
Hello!
OK - I know you have to install the .NET Framework on the machine you want to run your .Net-Application on, because it is not native code in your MyApp.exe. Now there's a tool called "Ngen.exe", which builds native code from any assembly. You will find the result then in your assembly-cache under
\%WINDIR%\assembly\NativeImages1_vx.x.xxx\MyApp\xxxxx\ (use Command-Prompt)
If you copy this native-code-file to another directory and start it, it only says, that it is no real Win32 program.
Could it be possible, to convert all used assemblies to native code and then run them without the framework? Or am I absolutely wrong?
|
|
|
|
|
That's not quite right.
Here's my take on the ngen util.
It does the complete JIT-compile for your EXE, but doesn't fold in the necessary .NET FCL classes. IE your app will still be xKB + 20 MB. 
If it did do what you suggested, al a Delphi, then there would be no need for the .NET framework.
Cheers,
Simon
"I get paid for my brain and my thinking in several obscure worlds", Olli, The Lounge
|
|
|
|
|
|
I just got started writing Windows-Apps in C++ and C#. The .Net concept seems to me much easier, exspecially because it has a "real & full" object oriented structure and not that confusing ResourceFile-concept of MFC. If I use a button, I can see how it is instantiated, properties are set etc. As a bottom up C++ Learner it is somehow confusing to me, to describe Buttons etc. in Resourcefiles instead of coding them into real c++ sourcecode. The big disadvantage I see at the moment is, that even if you want to distribute a small Tool, you force the user to install the whole .NET framework. But maybe in some months, nearly every Windows-System will have this Framework already installed.
My Question is now: As a Newbie, should I better continue writing in C# or C++/MFC? And in this context, is it possible to use some more "advanced" features in .Net like playing sounds, use external dlls (lame, zip etc.) or accessing the serial port for example?
Thanx for your opinions
Mario
|
|
|
|
|
You should learn both. .NET makes things easy, but C++ is a more powerful tool. You can't know too much, so don't feel you need any limits, just learn anything you can.
Christian
The tragedy of cyberspace - that so much can travel so far, and yet mean so little.
"I'm somewhat suspicious of STL though. My (test,experimental) program worked first time. Whats that all about??!?!
- Jon Hulatt, 22/3/2002
|
|
|
|
|
OK, thats absolutely right. Now here's the big but: Time. I think I've to decide which language to use (which Package I buy for my own). Maybe I continue with C++/MFC, because as my projects may get bigger, I don't want to hit on any limits and then rewrite the whole stuff in another language/environment.
|
|
|
|
|
If there is a Win32 API you want to call, you can call it in your .NET application. With that said you can do just about anything with .NET that you can with C/C++ the question now becomes, should you?
You have to remember that a .NET app will run about 80-90% slower than the C/C++ app that does the same thing. If your program can tolerate that then there isn't any reason not to use it unless you need to target Win95.
James
Sonork: Hasaki
"I left there in the morning
with their God tucked underneath my arm
their half-assed smiles and the book of rules.
So I asked this God a question
and by way of firm reply,
He said - I'm not the kind you have to wind up on Sundays."
"Wind Up" from Aqualung, Jethro Tull 1971
|
|
|
|
|
Good hint- Thanx. Maybe I'll call ngen on all my assemblies first to speed up the whole thing. On todays PCs a "normal" App (no big calculations etc.) should work, I think. And as I learned how to import extern dlls today - there doesn't seem to be any big restrictions left. Hopefully the C#-community will get as big as the MFC-Scene is today - that helps a lot on solving problems.
Mario
|
|
|
|
|
James T. Johnson wrote:
You have to remember that a .NET app will run about 80-90% slower than the C/C++ app that does the same thing
I think this is an exaggeration. Where did you get that information ?
There are so many different types of program.. that statement sounds unreal.
No offense
Andres Manggini.
Buenos Aires - Argentina.
|
|
|
|
|
I'm pretty sure the figure came from the DOTNET mailing list from either someone at MS or John Lam who did a lot of different tests regarding IL -> x86 generation; I'm leaning towards it being John because that would have been the context to get the figure out.
If thats the case the 80-90% figure is comparing the x86 code that the JIT produces versus the C++ x86 code that is produced.
James
Simplicity Rules!
|
|
|
|
|
The .NET Framework is now on Windows Update, at least for Win2K systems; I just checked Windows Update on my dad's computer (WinXP) and it wasn't listed there yet.
Thanks to Chris Anderson on the DOTNET mailing list for pointing out that it was on there
James
Sonork: Hasaki
"I left there in the morning
with their God tucked underneath my arm
their half-assed smiles and the book of rules.
So I asked this God a question
and by way of firm reply,
He said - I'm not the kind you have to wind up on Sundays."
"Wind Up" from Aqualung, Jethro Tull 1971
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
