Instantiatin .NET 2.0 object from Net 1.1

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Diestl replied

16 January 2007, 22:26
Have you tried using reflection to load the assembly then create an instance of the class you need?
Leave a comment:
Weltchy replied

15 January 2007, 16:03
Originally posted by DimPrawn

My understanding is it is not possible for a 1.1 application to reference a 2.0 assembly. This is because the application will be using 1.1 runtime and one process can only host one runtime.

A 2.0 application can however reference a 1.1 assembly, in which case the 1.1 assembly will run under the 2.0 runtime.

HTH

That was my initial thoughts as well, but I wasn't 100% sure!!! The thought did cross my mind to wrap the 2.0 assembly in a com wrapper and then call that from 1.1, but that certainly would not be best practise, let alone possible!!!!
Leave a comment:
ASB replied

15 January 2007, 15:52
Originally posted by DimPrawn

My understanding is it is not possible for a 1.1 application to reference a 2.0 assembly. This is because the application will be using 1.1 runtime and one process can only host one runtime.

A 2.0 application can however reference a 1.1 assembly, in which case the 1.1 assembly will run under the 2.0 runtime.

HTH

I thought that was likely to be the answer.

I was considering the possibility of making my root executable a 2.0 app. This then calls the 1.1 assemblies. My hope then being that I could do a gradual migration. Unfortunately this runs out of steam pretty quick because at the least I'll br producing wrappers for all sorts of things all over the place. Also there isn't a 2.0 version (well not one the I've got a licence for) of the main language.

Still looks like a good time to blag that 2.0 and C# training.

Cheers,
Leave a comment:
DimPrawn replied

15 January 2007, 15:44
My understanding is it is not possible for a 1.1 application to reference a 2.0 assembly. This is because the application will be using 1.1 runtime and one process can only host one runtime.

A 2.0 application can however reference a 1.1 assembly, in which case the 1.1 assembly will run under the 2.0 runtime.

HTH
Leave a comment:
ASB started a topic Instantiatin .NET 2.0 object from Net 1.1

15 January 2007, 14:37
Instantiatin .NET 2.0 object from Net 1.1

I must be missing something here. Possibly something as elementart as "you can't do that".

I have a .NET 2.0 assembly which happens to be C#.

I have a .NET 1.1 which happens to be VB.

I want to create an instance of the .NET 2.0 object from the VB. [It actually happens by calling a createinstance method on a different 1.1. C# object].

Is there anything I need to do configuration wise to enable this to happen because it doesn't work (no idea if there are any exceptions or anytrhing because they may well be swallowed elsewhere).

If I create a VB VS 2005 project everything works fine. i.e.

-> VS.NET 2005 VB to -> VS.NET 2003 C# -> VS.NET 2005
Tags: None