Getting C++.NET 2002 outside US in Germany

[Anonymous]

Germany. Where about and what is Germany ? I just wonder where to get C++.NET 2002 from. All vendors tell me C++.NET 2002? No! Can have 2003, no problem. Read something about downgrading. No problem. Got C++.NET 2003 Standard, EN. No money to throw away. Downgrade. Sorry! Must have Prof or Enterprise. Idea was: order from Microsoft US. Sorry they don't sell software outside US. My name is NOT Bin Laden. So what. Wait until Audodesk comes out with ACAD 2006 (they are late) Any other German speaking fellow around here? Cheers Dieter

[Anonymous]

try ebay

[Anonymous]

Hope you are not joking! Did that already. Check it yourself. Great. It's obviously a game. You by new software and a pay again for downgrading. Is this world still NORMAL ???? Fed up Dieter lorier wrote: > try ebay >

[Anonymous]

"Dieter Berger" schrieb: > Germany. Where about and what is Germany ? > I just wonder where to get C++.NET 2002 from. > All vendors tell me C++.NET 2002? No! Can have 2003, no problem. > Read something about downgrading. No problem. > Got C++.NET 2003 Standard, EN. > No money to throw away. Downgrade. Sorry! Must have Prof or Enterprise. > Idea was: order from Microsoft US. Sorry they don't sell > software outside US. My name is NOT Bin Laden. > So what. Wait until Audodesk comes out with ACAD 2006 (they are late) > Any other German speaking fellow around here? > > Cheers > Dieter Dieter, as long as you don't use MFC you can compile with the compiler which comes with the Microsoft .NET Framework SDK 1.0. Maybe you have some old CD floating around with it, else you can download it from Microsoft (but it is big). I think you need SP2 as well (not sure about that). I compiled successfully my apps with this compiler. I don't have net 2003, only MSVC++ 6.0 Standard. In MSVC++ 6.0 I opened my projects and created make files for them (Projekt->Makefile exportieren). Then I edited manually this make files, changed every occurance of 'vc60' to 'vc70', changed the pathes for the objectarx includes and libs. You must use cl.exe, link.exe and nmake.exe from vc7, but midl.exe and rc.exe from VC6 work fine. I'm sure you know that you compile a make file with 'nmake '. One of my arx-apps is a com server (doesn't use MFC) which has to be linked with acedapi.lib. This lib seems to be dependend of mfc70.lib, mfcs70.lib and atls.lib which I don't have. So I copied and renamed this 3 files: Mfc42.lib -> Mfc70.lib Mfcs42.lib -> Mfcs70.lib Atl.lib -> Atls.lib and then my apps compiled smooth and everything seems to be fine (but I have done that yesterday so I couldn't test it a lot). Stephan

[Anonymous]

Thanks a lot (!) Stephan I don't use MFC as well. Things I can't do with VLisp I use ARX for. Over the years the code accumulated and I saw it all gone for no reason. I'll give it a try next week or so. In case you are curious (but give me some time): [email protected] Thanks again Dieter Stephan Koster wrote: > "Dieter Berger" schrieb: > >> Germany. Where about and what is Germany ? >> I just wonder where to get C++.NET 2002 from. >> All vendors tell me C++.NET 2002? No! Can have 2003, no problem. >> Read something about downgrading. No problem. >> Got C++.NET 2003 Standard, EN. >> No money to throw away. Downgrade. Sorry! Must have Prof or Enterprise. >> Idea was: order from Microsoft US. Sorry they don't sell >> software outside US. My name is NOT Bin Laden. >> So what. Wait until Audodesk comes out with ACAD 2006 (they are late) >> Any other German speaking fellow around here? >> >> Cheers >> Dieter > > > Dieter, > > as long as you don't use MFC you can compile with the compiler > which comes with the Microsoft .NET Framework SDK 1.0. Maybe you have some > old CD floating around with it, else you can download it from Microsoft > (but > it is big). I think you need SP2 as well (not sure about that). > I compiled successfully my apps with this compiler. > I don't have net 2003, only MSVC++ 6.0 Standard. > In MSVC++ 6.0 I opened my projects and created make files for them > (Projekt->Makefile exportieren). Then I edited manually this make files, > changed every occurance of 'vc60' to 'vc70', changed the pathes for the > objectarx includes and libs. > You must use cl.exe, link.exe and nmake.exe from vc7, but midl.exe and > rc.exe > from VC6 work fine. I'm sure you know that you compile a make file with > 'nmake '. > One of my arx-apps is a com server (doesn't use MFC) which has to be > linked with > acedapi.lib. This lib seems to be dependend of mfc70.lib, mfcs70.lib and > atls.lib > which I don't have. So I copied and renamed this 3 files: > Mfc42.lib -> Mfc70.lib > Mfcs42.lib -> Mfcs70.lib > Atl.lib -> Atls.lib > and then my apps compiled smooth and everything seems to be fine (but I > have > done that yesterday so I couldn't test it a lot). > > Stephan

[Anonymous]

"Stephan Koster" wrote > One of my arx-apps is a com server (doesn't use MFC) which has to be linked with > acedapi.lib. This lib seems to be dependend of mfc70.lib, mfcs70.lib and atls.lib > which I don't have. So I copied and renamed this 3 files: > Mfc42.lib -> Mfc70.lib > Mfcs42.lib -> Mfcs70.lib > Atl.lib -> Atls.lib > and then my apps compiled smooth and everything seems to be fine (but I have > done that yesterday so I couldn't test it a lot). Do you actually think this is going to work? If as you say, it 'seems to be fine', I would venture to guess that you can say this, only because of limited-to-no testing, or because your ARX COM server is fairly limited in what it does. Doing what you describe above is absolutey ill-advised and is basically nothing but begging for trouble. -- http://www.caddzone.com AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005 http://www.acadxtabs.com

[Anonymous]

Hi Tony, still left out in the dark. Your remark is absolutely correct. But what else can I do! I've decided to give it a try with .NET 2003. As told, nothing fancy about my ARX: basic things like IPC, keybord hooks, WIN-API, convex and non-convex polygons and number crunching (structural engineering). Imported my first V6 project, changed some incs to ...16 or removed them alltogether. That one seemed to compile, appart from well known error messages which I habitually ignore. Haven't testet it yet. Will do that on monday, when I've got more energy and nerves. But the fundamental question is still not answered: what if all fails ? Dieter

[Anonymous]

I got 2002 for $70 and 2003 upgrade for $170 on ebay

[Anonymous]

I don't know if I'd consider IPC or keyboard hooks to be "basic things"...but... If you can do what you need to do using just AutoCAD's .NET API (I think COM Interop is OK too), then Visual Studio 2003 will work. Visual Studio 2002 is *REQUIRED* for any non-trivial ObjectARX development. By "non-trivial" I mean anything that results in a call C++'s operator new(); so if all you're using is the old C-style ADS APIs, you might be able to use Visual Studio 2003 too. Dan wrote in message news:41b9a1a5$1_3@newsprd01... > Hi Tony, > still left out in the dark. Your remark is absolutely correct. > But what else can I do! > I've decided to give it a try with .NET 2003. As told, nothing fancy > about my ARX: basic things like IPC, keybord hooks, WIN-API, convex and > non-convex polygons and number crunching (structural engineering). > Imported my first V6 project, changed some incs to ...16 or removed them > alltogether. That one seemed to compile, appart from well known error > messages which I habitually ignore. Haven't testet it yet. Will do that on > monday, when I've got more energy and nerves. > But the fundamental question is still not answered: what if all fails ? > > Dieter >

[Anonymous]

wrote in message news:41b74f75_2@newsprd01... > I just wonder where to get C++.NET 2002 from. > All vendors tell me C++.NET 2002? No! Can have 2003, no problem. > Read something about downgrading. No problem. > Got C++.NET 2003 Standard, EN. > No money to throw away. Downgrade. Sorry! Must have Prof or Enterprise. > Idea was: order from Microsoft US. Sorry they don't sell > software outside US. Dieter, Have you already seen this information which asks for you to contact the MS subsidiary in your country? http://msdn.microsoft.com/visualc/previous/downgrade.aspx There was also the free C++ toolkit from MS, but I seem to only find the 2003 version right now: http://msdn.microsoft.com/visualc/vctoolkit2003/ Dig around till you can find the 2002 toolkit somewhere. Once you have that, you can tell your 2003 IDE to use the 2002 compiler and linker by changing the paths in the IDE. -- Himanshu Gohel. Civil3D Team, Autodesk, Inc. Autodesk Civil3D Product Information <>

[Anonymous]

Quick follow-up to my own message... "H Gohel" wrote in message news:41b9c3a4$1_3@newsprd01... > There was also the free C++ toolkit from MS, but I seem to only find the > 2003 version right now: I may may be mistaken about this. There was a previous version, but that was apparently also VC++ Toolkit 2003 version 1.0 as opposed to the current version 1.01. The compilers have changed from 1.0 to 1.01, but you will have to find out for your self if the older version was 2002 or not (I doubt it). All the best, -- Himanshu

[Anonymous]

Can it be, that you must buy a software package from ebay because you can't order it from a dealer ? We are not talking about some exotic stuff, or do you think a 2 year old software package is exotic. Dieter

[Anonymous]

Tony Tanzillo wrote: >>One of my arx-apps is a com server (doesn't use MFC) which has to be linked with >>acedapi.lib. This lib seems to be dependend of mfc70.lib, mfcs70.lib and atls.lib >>which I don't have. So I copied and renamed this 3 files: >>Mfc42.lib -> Mfc70.lib >>Mfcs42.lib -> Mfcs70.lib >>Atl.lib -> Atls.lib >>and then my apps compiled smooth and everything seems to be fine (but I have >>done that yesterday so I couldn't test it a lot). > > Do you actually think this is going to work? If as you say, > it 'seems to be fine', I would venture to guess that you can > say this, only because of limited-to-no testing, or because > your ARX COM server is fairly limited in what it does. What I have done is a hack and I did not even expect it to compile. But after doing some more tests everything is working ok. Of course that doesn't mean that it should work for any other app than my 'fairly limited' com server. As I said above my com server doesn't use MFC, I'm quite sure that the hack will not work if one uses MFC. To say it clear: I do not advise to do the same. Everyone who has .net 2002 available should use it to compile his apps in the official way. The hack above was an experiment which works for me to my own surprise. > Doing what you describe above is absolutey ill-advised and is > basically nothing but begging for trouble. Is this simply your opinion or do you have some facts to confirm that? Stephan

[Anonymous]

http://msdn.microsoft.com/vbasic/previous/downgrade.aspx Twenty Bucks...Not bad...Have not tried yet but soon... wrote in message news:41b74f75_2@newsprd01... > Germany. Where about and what is Germany ? > I just wonder where to get C++.NET 2002 from. > All vendors tell me C++.NET 2002? No! Can have 2003, no problem. > Read something about downgrading. No problem. > Got C++.NET 2003 Standard, EN. > No money to throw away. Downgrade. Sorry! Must have Prof or Enterprise. > Idea was: order from Microsoft US. Sorry they don't sell > software outside US. My name is NOT Bin Laden. > So what. Wait until Audodesk comes out with ACAD 2006 (they are late) > Any other German speaking fellow around here? > > Cheers > Dieter > > > > > >

[Anonymous]

>>>Atl.lib -> Atls.lib Are you also not using ATL? -- http://www.caddzone.com AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005 http://www.acadxtabs.com "Stephan Koster" wrote in message news:41bae437$1_3@newsprd01... > Tony Tanzillo wrote: > >>>One of my arx-apps is a com server (doesn't use MFC) which has to be linked with >>>acedapi.lib. This lib seems to be dependend of mfc70.lib, mfcs70.lib and atls.lib >>>which I don't have. So I copied and renamed this 3 files: >>>Mfc42.lib -> Mfc70.lib >>>Mfcs42.lib -> Mfcs70.lib >>>and then my apps compiled smooth and everything seems to be fine (but I have >>>done that yesterday so I couldn't test it a lot). >> >> Do you actually think this is going to work? If as you say, >> it 'seems to be fine', I would venture to guess that you can >> say this, only because of limited-to-no testing, or because >> your ARX COM server is fairly limited in what it does. > > What I have done is a hack and I did not even expect it to compile. > But after doing some more tests everything is working ok. Of course > that doesn't mean that it should work for any other app than my > 'fairly limited' com server. > As I said above my com server doesn't use MFC, I'm quite sure that the > hack will not work if one uses MFC. > > To say it clear: I do not advise to do the same. Everyone who has > .net 2002 available should use it to compile his apps in the official > way. The hack above was an experiment which works for me to my > own surprise. > >> Doing what you describe above is absolutey ill-advised and is >> basically nothing but begging for trouble. > > Is this simply your opinion or do you have some facts to confirm that? > > Stephan

[Anonymous]

Tony Tanzillo schrieb: >>>>Atl.lib -> Atls.lib > > > Are you also not using ATL? > Of course I'm using ATL, but the project doesn't link to Atl.lib

[Anonymous]

Hi Paul, to get it straight, you refer to vbasic. C++ is likewise. This is from microsoft usa-homepage: Downgrade Information for Visual C++ "Outside the United States and Canada, please contact your local Microsoft subsidiary" .... "In addition, some previous versions of Visual C++ may also be available through resellers. Please contact your local reseller for details." (read my 1. thread) Cheers Dieter

[Anonymous]

Yea..Figured must be C++ also...Anyone download yet...? wrote in message news:41bf3d14$1_1@newsprd01... > Hi Paul, > to get it straight, you refer to vbasic. C++ is likewise. > > This is from microsoft usa-homepage: > > Downgrade Information for Visual C++ > > "Outside the United States and Canada, please contact your local Microsoft > subsidiary" > .... > > "In addition, some previous versions of Visual C++ may also be available > through resellers. Please contact your local reseller for details." > (read my 1. thread) > > Cheers > Dieter > > > > > >

[Anonymous]

No 'cause you can't. Ever signed a life insurance? Dont't read the footnotes, you'll spoil your eyes. Never mind Dieter Paul Richardson wrote: > Yea..Figured must be C++ also...Anyone download > yet...? > wrote in message news:41bf3d14$1_1@newsprd01... > >>Hi Paul, >>to get it straight, you refer to vbasic. C++ is likewise. >> >>This is from microsoft usa-homepage: >> >>Downgrade Information for Visual C++ >> >>"Outside the United States and Canada, please contact your local Microsoft >>subsidiary" >>.... >> >>"In addition, some previous versions of Visual C++ may also be available >>through resellers. Please contact your local reseller for details." >>(read my 1. thread) >> >>Cheers >>Dieter >> >> >> >> >> >> >> > >