I have dl'd and installed the .net framework 3.0 in hopes of gaining access to the system.net.mail namespace but I still cannot find it. I cannot reference it, import it, or use it in any other fashion.
Not sure. I installed .NET 2.0 and it wasn't there either, so I bumped up to 3.0 and it's still not there. I can't imagine that I'm the only one experiencing this problem, but I cannot determine what, if anything, I have not referenced correctly.
When I try to add a reference to my project, System.Net is not even listed on the .NET tab (it goes from System.Messaging.Dll to System.Runtime.Remoting), nor is it on the COM tab (it goes from System.Drawing.dll to System.Windows.Forms.dll). I've even gone so far as to try to find it w/ an Import statement but no luck there either.
Then you are doing something wrong because it is there in 2.0 and since 3.0 is just an extension of 2.0 it is there also.
Christiaan Baes
Belgium
My Blog
"In a system where you can define a factor as part of a third factor, you need another layer to check the main layer in case the second layer is not the base unit." - jrbarnett
What is it that I could be doing wrong??? I've tried to reference it, import it, show it, access it, find it and it's just not there. Even when I view the System reference in the Object Browser, System.Net.Mail does not show up. I can't find it anywhere.
I've tried reinstalling the .net framework 3.0 and it's still not there.
The 3.0 framework won't help in this instance since the system namespace resides in the 2.0 part. You still need that.
And I have no idea what you have done wrong, I and rick can only see that it works for us.
Christiaan Baes
Belgium
My Blog
"In a system where you can define a factor as part of a third factor, you need another layer to check the main layer in case the second layer is not the base unit." - jrbarnett
OK. That would mean that I would have to reinstall .net fw 2.0. I wonder if it will let me reinstall 2.0 if I'm already on 3.0. I guess I will find out.
I uninstalled .net fw 3.0
I reinstalled (repaired) .net fw 2.0
Set references to "System" and "System.Net"
Entered "Imports System"
Entered "Imports System.Net"
Entered "Imports System.Net.Mail" but I get an error on this line stating that the namespace cannot be found
But I still have one unresolved question: Since I am using VS2003, and it is still referencing .net fw 1.1, how can I get it to recognize the newer .net framework, or is this even possible?
You see, if you had given us all the details we could have told you that.
Christiaan Baes
Belgium
My Blog
"In a system where you can define a factor as part of a third factor, you need another layer to check the main layer in case the second layer is not the base unit." - jrbarnett
No trbyrne, you can not use the 2.0 framework in VS 2002 or 2003. You can however download the express version of VS 2005, purchase an upgrade to 2005, go to a MS event and get a copy for free, or use a text editor and compile by hand.
My Blog
"In a system where you can define a factor as part of a third factor, you need another layer to check the main layer in case the second layer is not the base unit." - jrbarnett
Thanks for the help and advice. Had I known at the start that the version of VS played a role then, yes, I would certainly have mentioned it. Knowing what I know now, I have purchased an upgrade to VS 2005 pro. It's rather frustrating to know that MS makes you purchase the upgrade to take advantage of the new .net framework. But they are a business and this is one sure way of locking in income streams.
I can't say I fault them. 2K5 has a lot of functionality and features that 2k2/2k3 don't have. And programming labor does not come cheap. Framework 2 is a huge step up from the 1.0/1.1 platform, and the IDE needed a good number of changes and improvements to fully take advantage of those improvements. I would hardly call MS greedy because they were trying to find a way to pay teams upon teams of people for 2 years of labor.
Heck, they even released the express series for free!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.