PDA

View Full Version : API and .NET2.0


GuyR
2006-01-21, 11:42 PM
Can anyone answer this question all related to Revit V9 moving to .NET2.0:

1.. Can we run Revit V8.1 with .NET2.0 and use the 1.1 API?

Python for .NET is ready for release (has been for a while ;-) ) but I've been adding on some goodies. However I've just started to look at .NET2.0 implications, and there are some. I'm wondering if I should(can) target .NET2.0 and still be able to provide a Revit 8.1 version.

If 1.1 and 2.0 aren't compatible then we'll need a V8.1 release that is built on .NET2.0 I guess?

Any thoughts appreciated. Yes I know I could download .NET2.0 and try it but this potentially will stuff quite a lot of other applications on my PC.

Guy

GuyR
2006-01-23, 08:37 PM
Answers from my testing:

1. You can install and run .NET2.0 alongside .NET1.1

2.. Revit V8.1 will run with only .NET2.0 as long as there are no API commands in Revit.ini.

I get an error APIlink.dll if I try and load any 1.1 commands. So the API isn't backward compatible with .NET2.0 by my testing. Python for Revit not working with .NET2.0 ;-(

Guy

PeterJ
2006-01-23, 09:33 PM
Well if it is ready for release, please get it out there, Guy. Let people make their own mind up whether or not they require Net 2

GuyR
2006-01-23, 09:50 PM
Hi Peter,

I hear what you're saying but there isn't much point releasing python for Revit if it will only ever work with V8.1? Revit V9 will be NET2.0. So you won't have a choice ;-)

From research, most 1.1 applications should be backward compatible. Revit V8.1 API however doesn't seem to be without ADESK releasing a new APIlink.dll. I'd like to be able to at least confirm P4R will work with .NET2.0 if I can. I'm looking at other ways I can do that.

I'm well aware people and firms would like to get their hands on this but I also want to make sure it's the beginning of a longterm project developing productive opensource tools for users. Just a little longer...

Guy

oh yeah, it's been >25degC here, the beach(across the road) and sea temperature have been a far more enticing way to spend the evenings than coding ;-) ;-) Sorry......