.NET

[#1]

I installed 2006 on my system but support 2005 users. I built a VB.NET app
that opens some drawings and reads xrecord information. The solution has
no 2006 references and works perfectly on my system in 2005 and any system
that
has both 2005 and 2006 installed. But it gives flakey results on the
average
user's system that has not been touched by 2006.

I de-installed ACAD 2006 and recompiled without improvement. This sounds
like the vba problem where the 2004 type libraries were replaced with 2005
and you had to be extremely careful manually swap the libraries with batch
file
when you were working on an update for a 2004 system.

Does any one have a thought about what might be going on here so I can
develop for both 2005 and 2006 on the same computer?

Thanks, Ted

[#2]

look for Build for multiple Autocad versions, dated 18-5-2005, CArps
solution worked a treat.



Laurence

"TedSch" wrote in message
news:4873151@discussion.autodesk.com...
I installed 2006 on my system but support 2005 users. I built a VB.NET app
that opens some drawings and reads xrecord information. The solution has
no 2006 references and works perfectly on my system in 2005 and any system
that
has both 2005 and 2006 installed. But it gives flakey results on the
average
user's system that has not been touched by 2006.

I de-installed ACAD 2006 and recompiled without improvement. This sounds
like the vba problem where the 2004 type libraries were replaced with 2005
and you had to be extremely careful manually swap the libraries with batch
file
when you were working on an update for a 2004 system.

Does any one have a thought about what might be going on here so I can
develop for both 2005 and 2006 on the same computer?

Thanks, Ted

[#3]

What happens when it acts "flakey"? Can you describe the problem that you
are seeing?

Albert
"TedSch" wrote in message
news:4873151@discussion.autodesk.com...
I installed 2006 on my system but support 2005 users. I built a VB.NET app
that opens some drawings and reads xrecord information. The solution has
no 2006 references and works perfectly on my system in 2005 and any system
that
has both 2005 and 2006 installed. But it gives flakey results on the
average
user's system that has not been touched by 2006.

I de-installed ACAD 2006 and recompiled without improvement. This sounds
like the vba problem where the 2004 type libraries were replaced with 2005
and you had to be extremely careful manually swap the libraries with batch
file
when you were working on an update for a 2004 system.

Does any one have a thought about what might be going on here so I can
develop for both 2005 and 2006 on the same computer?

Thanks, Ted

[#4]

Albert,

I am showing a form with a listview grid which I am populating with
file name, path and information from a xrecord. Half of the drawings
I am trying to open in 2005 are throwing an error on a user's system
but open consistently when I run 2005 but also has a version of 2006
installed. I catch the error and note the file as "skipped".

- Ted

"Albert Szilvasy" wrote in message
news:4873243@discussion.autodesk.com...
What happens when it acts "flakey"? Can you describe the problem that you
are seeing?

Albert
"TedSch" wrote in message
news:4873151@discussion.autodesk.com...
I installed 2006 on my system but support 2005 users. I built a VB.NET app
that opens some drawings and reads xrecord information. The solution has
no 2006 references and works perfectly on my system in 2005 and any system
that
has both 2005 and 2006 installed. But it gives flakey results on the
average
user's system that has not been touched by 2006.

I de-installed ACAD 2006 and recompiled without improvement. This sounds
like the vba problem where the 2004 type libraries were replaced with 2005
and you had to be extremely careful manually swap the libraries with batch
file
when you were working on an update for a 2004 system.

Does any one have a thought about what might be going on here so I can
develop for both 2005 and 2006 on the same computer?

Thanks, Ted

[#5]

Laurence,

Thanks. I looked but missed it. Shouldn't we be getting a proactive
ADN newsletter about this and a switch tool that lets us toggle between
the 2 environments made by the folks that created the problem.

- Ted


"Laurence Skoropinski" wrote in message
news:4873208@discussion.autodesk.com...
look for Build for multiple Autocad versions, dated 18-5-2005, CArps
solution worked a treat.



Laurence

"TedSch" wrote in message
news:4873151@discussion.autodesk.com...
I installed 2006 on my system but support 2005 users. I built a VB.NET app
that opens some drawings and reads xrecord information. The solution has
no 2006 references and works perfectly on my system in 2005 and any system
that
has both 2005 and 2006 installed. But it gives flakey results on the
average
user's system that has not been touched by 2006.

I de-installed ACAD 2006 and recompiled without improvement. This sounds
like the vba problem where the 2004 type libraries were replaced with 2005
and you had to be extremely careful manually swap the libraries with batch
file
when you were working on an update for a 2004 system.

Does any one have a thought about what might be going on here so I can
develop for both 2005 and 2006 on the same computer?

Thanks, Ted

[#6]

What is the error that you are getting?
Albert

"TedSch" wrote in message
news:4873530@discussion.autodesk.com...
Albert,

I am showing a form with a listview grid which I am populating with
file name, path and information from a xrecord. Half of the drawings
I am trying to open in 2005 are throwing an error on a user's system
but open consistently when I run 2005 but also has a version of 2006
installed. I catch the error and note the file as "skipped".

- Ted

"Albert Szilvasy" wrote in message
news:4873243@discussion.autodesk.com...
What happens when it acts "flakey"? Can you describe the problem that you
are seeing?

Albert
"TedSch" wrote in message
news:4873151@discussion.autodesk.com...
I installed 2006 on my system but support 2005 users. I built a VB.NET app
that opens some drawings and reads xrecord information. The solution has
no 2006 references and works perfectly on my system in 2005 and any system
that
has both 2005 and 2006 installed. But it gives flakey results on the
average
user's system that has not been touched by 2006.

I de-installed ACAD 2006 and recompiled without improvement. This sounds
like the vba problem where the 2004 type libraries were replaced with 2005
and you had to be extremely careful manually swap the libraries with batch
file
when you were working on an update for a 2004 system.

Does any one have a thought about what might be going on here so I can
develop for both 2005 and 2006 on the same computer?

Thanks, Ted

[#7]

By de-installing everything autocad on my pc and adding back 2005,
I was able to reproduce the error on the same machine where my VS
is located - tedious.

But the good news is that I found the code errored on db.ReadDwgFile
statement. I left off the arguments when I created the db object.

'db = New Database 'old and error prone
db = New Database(False, True) 'works - not sure why the settings are:
false, true
Try
db.ReadDwgFile(DwgInfoSet.DwgFullName, IO.FileShare.Read, False, Nothing)

Because 2006 was on my system, the (false, true) arguments
weren't necessary - apparently. But what's confusing, on a
2005 only system, only 50% of the drawings produced the error.

It would be wonderful if you could explain the reason for these settings
and why the error seems to affect only certain drawings

Thanks, Ted
WD Partners


"Albert Szilvasy" wrote in message
news:4873900@discussion.autodesk.com...
What is the error that you are getting?
Albert

"TedSch" wrote in message
news:4873530@discussion.autodesk.com...
Albert,

I am showing a form with a listview grid which I am populating with
file name, path and information from a xrecord. Half of the drawings
I am trying to open in 2005 are throwing an error on a user's system
but open consistently when I run 2005 but also has a version of 2006
installed. I catch the error and note the file as "skipped".

- Ted

"Albert Szilvasy" wrote in message
news:4873243@discussion.autodesk.com...
What happens when it acts "flakey"? Can you describe the problem that you
are seeing?

Albert
"TedSch" wrote in message
news:4873151@discussion.autodesk.com...
I installed 2006 on my system but support 2005 users. I built a VB.NET app
that opens some drawings and reads xrecord information. The solution has
no 2006 references and works perfectly on my system in 2005 and any system
that
has both 2005 and 2006 installed. But it gives flakey results on the
average
user's system that has not been touched by 2006.

I de-installed ACAD 2006 and recompiled without improvement. This sounds
like the vba problem where the 2004 type libraries were replaced with 2005
and you had to be extremely careful manually swap the libraries with batch
file
when you were working on an update for a 2004 system.

Does any one have a thought about what might be going on here so I can
develop for both 2005 and 2006 on the same computer?

Thanks, Ted

[#8]

Calling the default constructor of Database (i.e. the one without arguments)
is the same as calling Database(true, true). You can't call ReadDwgFile on a
Database that already has the default elements (i.e. the first parameter is
true).
It is indeed quite interesting that only half of your drawings produced a
problem. Nevertheless, what you are doing now (i.e. passing false to the
first argument) is the right thing to do if you want to call ReadDwgFile on
the Database.

Albert

"TedSch" wrote in message
news:4874064@discussion.autodesk.com...
By de-installing everything autocad on my pc and adding back 2005,
I was able to reproduce the error on the same machine where my VS
is located - tedious.

But the good news is that I found the code errored on db.ReadDwgFile
statement. I left off the arguments when I created the db object.

'db = New Database 'old and error prone
db = New Database(False, True) 'works - not sure why the settings are:
false, true
Try
db.ReadDwgFile(DwgInfoSet.DwgFullName, IO.FileShare.Read, False, Nothing)

Because 2006 was on my system, the (false, true) arguments
weren't necessary - apparently. But what's confusing, on a
2005 only system, only 50% of the drawings produced the error.

It would be wonderful if you could explain the reason for these settings
and why the error seems to affect only certain drawings

Thanks, Ted
WD Partners


"Albert Szilvasy" wrote in message
news:4873900@discussion.autodesk.com...
What is the error that you are getting?
Albert

"TedSch" wrote in message
news:4873530@discussion.autodesk.com...
Albert,

I am showing a form with a listview grid which I am populating with
file name, path and information from a xrecord. Half of the drawings
I am trying to open in 2005 are throwing an error on a user's system
but open consistently when I run 2005 but also has a version of 2006
installed. I catch the error and note the file as "skipped".

- Ted

"Albert Szilvasy" wrote in message
news:4873243@discussion.autodesk.com...
What happens when it acts "flakey"? Can you describe the problem that you
are seeing?

Albert
"TedSch" wrote in message
news:4873151@discussion.autodesk.com...
I installed 2006 on my system but support 2005 users. I built a VB.NET app
that opens some drawings and reads xrecord information. The solution has
no 2006 references and works perfectly on my system in 2005 and any system
that
has both 2005 and 2006 installed. But it gives flakey results on the
average
user's system that has not been touched by 2006.

I de-installed ACAD 2006 and recompiled without improvement. This sounds
like the vba problem where the 2004 type libraries were replaced with 2005
and you had to be extremely careful manually swap the libraries with batch
file
when you were working on an update for a 2004 system.

Does any one have a thought about what might be going on here so I can
develop for both 2005 and 2006 on the same computer?

Thanks, Ted

[#9]

Thanks!

"Albert Szilvasy" wrote in message
news:4874514@discussion.autodesk.com...
Calling the default constructor of Database (i.e. the one without arguments)
is the same as calling Database(true, true). You can't call ReadDwgFile on a
Database that already has the default elements (i.e. the first parameter is
true).
It is indeed quite interesting that only half of your drawings produced a
problem. Nevertheless, what you are doing now (i.e. passing false to the
first argument) is the right thing to do if you want to call ReadDwgFile on
the Database.

Albert

"TedSch" wrote in message
news:4874064@discussion.autodesk.com...
By de-installing everything autocad on my pc and adding back 2005,
I was able to reproduce the error on the same machine where my VS
is located - tedious.

But the good news is that I found the code errored on db.ReadDwgFile
statement. I left off the arguments when I created the db object.

'db = New Database 'old and error prone
db = New Database(False, True) 'works - not sure why the settings are:
false, true
Try
db.ReadDwgFile(DwgInfoSet.DwgFullName, IO.FileShare.Read, False, Nothing)

Because 2006 was on my system, the (false, true) arguments
weren't necessary - apparently. But what's confusing, on a
2005 only system, only 50% of the drawings produced the error.

It would be wonderful if you could explain the reason for these settings
and why the error seems to affect only certain drawings

Thanks, Ted
WD Partners


"Albert Szilvasy" wrote in message
news:4873900@discussion.autodesk.com...
What is the error that you are getting?
Albert

"TedSch" wrote in message
news:4873530@discussion.autodesk.com...
Albert,

I am showing a form with a listview grid which I am populating with
file name, path and information from a xrecord. Half of the drawings
I am trying to open in 2005 are throwing an error on a user's system
but open consistently when I run 2005 but also has a version of 2006
installed. I catch the error and note the file as "skipped".

- Ted

"Albert Szilvasy" wrote in message
news:4873243@discussion.autodesk.com...
What happens when it acts "flakey"? Can you describe the problem that you
are seeing?

Albert
"TedSch" wrote in message
news:4873151@discussion.autodesk.com...
I installed 2006 on my system but support 2005 users. I built a VB.NET app
that opens some drawings and reads xrecord information. The solution has
no 2006 references and works perfectly on my system in 2005 and any system
that
has both 2005 and 2006 installed. But it gives flakey results on the
average
user's system that has not been touched by 2006.

I de-installed ACAD 2006 and recompiled without improvement. This sounds
like the vba problem where the 2004 type libraries were replaced with 2005
and you had to be extremely careful manually swap the libraries with batch
file
when you were working on an update for a 2004 system.

Does any one have a thought about what might be going on here so I can
develop for both 2005 and 2006 on the same computer?

Thanks, Ted