Hello,
Sorry if this is a brain dead question I did attempt to figure out why this was happening in the news groups and msdn first.
I am a bit new to VC++ 7 (.NET) and I am attempting to use tinyXML in a project of mine in order to read and parse some well formed XHTML table data from a file - but I havent even gotten that far yet. I added the 3 cpp files and the header and I've included the .h into my main and I am getting the following linker error:
as soon as I try to define a variable of type TiXmlDocument in my main. Can you point me in the right direction. Again sorry for the newbie-ness of this query and thanks for any assistance. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-04-23
I forgot to mention that when I downloaded version 2.0 and tried to open it (the dsp file) in VC++7 -- it asks to convert it and when I say yes it says the project file is corrupt. Hence me just attempting to load it directly into my project. Looking at the dsp file in a text editor it seems normal...??
Also, I should have tried this before, but version 1.2.4 seems to build fine in VC++7 .NET and seems to have the functionality I require (from the docs) yet I am not 100% certain what fixes or features 2 has that 1.2.4 doesn't? In any event, I should be able to use 1.2.4, yet would still like to know what I did wrong (if anything) with 2.0?
thanks again,
Sam
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-04-24
I think I've figured it out. It was something dumb as I expected. I accidentally left Assembly support /clr on inside the Project Properties in VC++ 7 .NET. Turning that off makes the linker error disappear. (I've been doing alot of managed/unmanaged code projects so didn't notice I left it on here when I didnt need it)
You may want to add that to an FAQ. Don't know how many others are using the .NET compiler??
Btw I still would like some feedback on the V2.0 project file of TinyXML being corrupt. If all I need is to read a text file and parse some well-formed XHTML tables is there any reason to use v2 over 1.2.4?
thanks,
Sam
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I haven't heard about the v2.0 project file being corrupt -- that may be a flaw in the build process when the releases are made. I'll have to look to see if the build script sets the EOL correctly. Thanks for the tip.
As for as the .NET compiler, I was even sure from microsofts docs that it supported C++. When I read their web page it sounded like they still used VC6 for C work, so I haven't even looked in to it. If they've revved the C++ IDE I'd be interested. But to answer your question, I haven't looked at it.
lee
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2002-04-28
Although I personally haven't been using VC6 much I would certainly say that the IDE in VC7 (from the professional edition of Visual Studio .NET that I am using - not enterprise) is very good.
The intellisense is better - collapsable editor in IDE for loops etc., dynamic help, integrated wysiwyg IE/frontpage html editor (way better than vis intercrap was) Overall totally worth the upgrade in my opinion. I am more productive in it.
The only thing I wish I had was the enterprise edition because that has UML to code generation from class diagrams from Visio. Check it out if you get a chance.
Thanks again for tinyXML though :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
Sorry if this is a brain dead question I did attempt to figure out why this was happening in the news groups and msdn first.
I am a bit new to VC++ 7 (.NET) and I am attempting to use tinyXML in a project of mine in order to read and parse some well formed XHTML table data from a file - but I havent even gotten that far yet. I added the 3 cpp files and the header and I've included the .h into my main and I am getting the following linker error:
test_display3d error LNK2020: unresolved token (0A000007) sprintf
as soon as I try to define a variable of type TiXmlDocument in my main. Can you point me in the right direction. Again sorry for the newbie-ness of this query and thanks for any assistance. :)
I forgot to mention that when I downloaded version 2.0 and tried to open it (the dsp file) in VC++7 -- it asks to convert it and when I say yes it says the project file is corrupt. Hence me just attempting to load it directly into my project. Looking at the dsp file in a text editor it seems normal...??
Also, I should have tried this before, but version 1.2.4 seems to build fine in VC++7 .NET and seems to have the functionality I require (from the docs) yet I am not 100% certain what fixes or features 2 has that 1.2.4 doesn't? In any event, I should be able to use 1.2.4, yet would still like to know what I did wrong (if anything) with 2.0?
thanks again,
Sam
I think I've figured it out. It was something dumb as I expected. I accidentally left Assembly support /clr on inside the Project Properties in VC++ 7 .NET. Turning that off makes the linker error disappear. (I've been doing alot of managed/unmanaged code projects so didn't notice I left it on here when I didnt need it)
You may want to add that to an FAQ. Don't know how many others are using the .NET compiler??
Btw I still would like some feedback on the V2.0 project file of TinyXML being corrupt. If all I need is to read a text file and parse some well-formed XHTML tables is there any reason to use v2 over 1.2.4?
thanks,
Sam
I haven't heard about the v2.0 project file being corrupt -- that may be a flaw in the build process when the releases are made. I'll have to look to see if the build script sets the EOL correctly. Thanks for the tip.
As for as the .NET compiler, I was even sure from microsofts docs that it supported C++. When I read their web page it sounded like they still used VC6 for C work, so I haven't even looked in to it. If they've revved the C++ IDE I'd be interested. But to answer your question, I haven't looked at it.
lee
Although I personally haven't been using VC6 much I would certainly say that the IDE in VC7 (from the professional edition of Visual Studio .NET that I am using - not enterprise) is very good.
The intellisense is better - collapsable editor in IDE for loops etc., dynamic help, integrated wysiwyg IE/frontpage html editor (way better than vis intercrap was) Overall totally worth the upgrade in my opinion. I am more productive in it.
The only thing I wish I had was the enterprise edition because that has UML to code generation from class diagrams from Visio. Check it out if you get a chance.
Thanks again for tinyXML though :)