.NET

[#1]

Thank god there is a dot net one now... Thank you Autodesk.


Anyone get Visual Studio 2005? Impressions?

[#2]

I'm still waiting for my beta copy to show up. Over the last month I have
been attempting the transistion from VB6 to .net.

[#3]

Depending upon you application, it works just fine for me.

[#4]

Hi,
Visual Studio 2005 Beta or Sharpdevelopp, no crash with autocad for the
moment.
it' s will be good


--
Laurent Falla
LFA Consulting Limited (Civil Design & development)
www.lfaconsulting.com


"AlmightySR" a écrit dans le message de news:
4848629@discussion.autodesk.com...
Thank god there is a dot net one now... Thank you Autodesk.


Anyone get Visual Studio 2005? Impressions?

[#5]

Apps done in Visual Studio 2005 that interface with
Autodesk.AutoCAD.Runtime.IExtensionApplication will crash with AutoCAD
2006+. If you limit your code to interaction with graphics, it should be
okay. If you start getting odd errors with cad, back down to 2003

-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon...

[#6]

The Version of #develop i have does not work with the managed wrapper classes of Autocad.
Visual C# Express Beta does work without any problems.

Roland

[#7]

Be sure to edit the acad.exe.config file to use the recommended version of dotnet. The default is to use the latest version and VS2005 will cause problems with 2006 based Autodesk based products.

I have heard of one person who could not run the layer command in 2006 (it is now a dot net ui) after installing VS2005. Editing acad.exe.config fixed the problem.

[#8]

Hi Mike,

What error are you seeing? I have test apps here that use this interface and
they work fine even when I compile them with VS2005 Beta2.

Albert

"Mike Tuersley" wrote in message
news:4848908@discussion.autodesk.com...
Apps done in Visual Studio 2005 that interface with
Autodesk.AutoCAD.Runtime.IExtensionApplication will crash with AutoCAD
2006+. If you limit your code to interaction with graphics, it should be
okay. If you start getting odd errors with cad, back down to 2003

-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon...

[#9]

.NET 2.0 Beta2 is very close to being compatible with AutoCAD 2006 (previous
betas and CTP build had a lot more compatibility issues). If you develop
.net applications using VS2005 you *must* run AutoCAD on .NET 2.0 Beta2.

The only problem I'm aware of at this point is an annoying error dialog that
comes up when you run the layer command. The layer dialog will come up after
you hit Ok to the error dialog. This is a bug in .NET 2.0 Beta2 that MS has
already fixed in their internal builds according to their bug tracking
system:

http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=cfe99155-48bc-4180-adbc-81c33212cc12

Please let me know if you experience any other issues running AutoCAD on
.NET 2.0 Beta2.

Albert

wrote in message news:4849146@discussion.autodesk.com...
Be sure to edit the acad.exe.config file to use the recommended version of
dotnet. The default is to use the latest version and VS2005 will cause
problems with 2006 based Autodesk based products.

I have heard of one person who could not run the layer command in 2006 (it
is now a dot net ui) after installing VS2005. Editing acad.exe.config fixed
the problem.

[#10]

Albert, just for clarification purposes, do you mean the framework when you
say ".Net 2.0 beta 2"?

--
----
Ed
----
"Albert Szilvasy" wrote in message
news:4849409@discussion.autodesk.com...
.NET 2.0 Beta2 is very close to being compatible with AutoCAD 2006 (previous
betas and CTP build had a lot more compatibility issues). If you develop
.net applications using VS2005 you *must* run AutoCAD on .NET 2.0 Beta2.

The only problem I'm aware of at this point is an annoying error dialog that
comes up when you run the layer command. The layer dialog will come up after
you hit Ok to the error dialog. This is a bug in .NET 2.0 Beta2 that MS has
already fixed in their internal builds according to their bug tracking
system:

http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=cfe99155-48bc-4180-adbc-81c33212cc12

Please let me know if you experience any other issues running AutoCAD on
.NET 2.0 Beta2.

Albert

wrote in message news:4849146@discussion.autodesk.com...
Be sure to edit the acad.exe.config file to use the recommended version of
dotnet. The default is to use the latest version and VS2005 will cause
problems with 2006 based Autodesk based products.

I have heard of one person who could not run the layer command in 2006 (it
is now a dot net ui) after installing VS2005. Editing acad.exe.config fixed
the problem.