Dot.Net 1.1 and 2.0

[ReneMarxis]

Hello

i have some question about a bigger VB project written in .Net 1.1

In short, we have to use the same sourcecode in 2 projects. The one
running on Net 1.1 (VS2003) and one in .Net 2.0 (VS2005)
We are using ClearCase as sourcecontrol and I'd like to ask if someone
has some experience in dealing with this kind of situation.

The solution is build of about 30 projects, all written in VB.Net 1.1
and consists of server and client parts. The serverparts are published
by interface-classes and called via COM from the clients.
Everything is written as windows-application or system-service. No web-
services are used at all.

As first step we would not use any functionalities from .Net 2.0 but
we will use them in future modules (of course only in the 2.0
project).

I can think of just 2 methods to accomplish this:
1) Try to pack as much funcitons into .Net 1.1 libraries and use those
libraries in both project
2) Try to share the sourcefiles in 2 different VS-projects by just
including them (probably use 2 CC-branches for every project and one
main-line of the sourcecode).

Any suggestions or comments?

_thanks in advance

rene

 

[Mr. Arnold]

Hello

i have some question about a bigger VB project written in .Net 1.1

In short, we have to use the same sourcecode in 2 projects. The one
running on Net 1.1 (VS2003) and one in .Net 2.0 (VS2005)
We are using ClearCase as sourcecontrol and I'd like to ask if someone
has some experience in dealing with this kind of situation.

The solution is build of about 30 projects, all written in VB.Net 1.1
and consists of server and client parts. The serverparts are published
by interface-classes and called via COM from the clients.
Everything is written as windows-application or system-service. No web-
services are used at all.

As first step we would not use any functionalities from .Net 2.0 but
we will use them in future modules (of course only in the 2.0
project).

I can think of just 2 methods to accomplish this:
1) Try to pack as much funcitons into .Net 1.1 libraries and use those
libraries in both project
2) Try to share the sourcefiles in 2 different VS-projects by just
including them (probably use 2 CC-branches for every project and one
main-line of the sourcecode).

Any suggestions or comments?

My comments are that you may have to branch the code, getting one version of
it to work with .NET 2.0.

I worked in one shop where they tried to take 1.1 code without change it and
make it run on 2.0. They told me they had problems in doing that, because
things with the application just didn't work right anymore on the 2.0
platform.

So what they did was that applications that existed and were 1.1 stayed
with 1.1 and would be revisited at a later time, while new projects were
done in 2.0.

 

[Egghead]

hmm,
Is there any reason you cannot upgrade your .net 1.1 to .net 2.0?
Anyway, you need to expose the .net 2.0 as COM object. Have fun when you try
to debug them

 

[ReneMarxis]

hmm,
Is there any reason you cannot upgrade your .net 1.1 to .net 2.0?
Anyway, you need to expose the .net 2.0 as COM object. Have fun when you try
to debug them

Yes
We are working in one validated environment where changeing even one
line of code can lead to a complete system-test ...
Thats why the guys want to have the old project running on the old
source (its allready validated) and the new one with the old-
sourcecode in dot-net 2.0.
This saves very much time when doing bugfixing, as only one (system)-
test needs to be done and if it succeds that change can be taken over
to the new project.

For now i did some tests and it seems to be possible to just build up
the projects from ground in .Net 2.0 and just add the *.vb and the
*.resx files from the old projects.
The only problem i have is that VS2005 copies the file from the
original directory to the project directory when adding it to the
new .Net 2.0 project.
I'll give it a try and change the vbproj file manualy and see if this
helps.

If this works i could just have one main-source-line in one vob and
build up the 2 projects from ground in 2 different vobs, add the
sourcefiles to the projects (ralitive path) and build the whole
solution.

I'll let you know if it works.

 

[Guest]

In VS you can actually choose whether to add the file or to create a link to
the file - when Add Existing Item dialog appears - notice there is a down
arrow on the Add button.
This way you may share the same file across multiple projects.

 

[ReneMarxis]

Ahhh many thanks Sergey

that helped a lot.