• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 165
  • Last Modified:

Mixing .NET 1.1 and .NET 2.0 assemblies/function calls

Hi experts,
I have a large Visual C++.NET 2003 managed code project, which is based on the .NET framework 1.1. Since I would like to use some features which are available just under the 2.0 framework (bulk insertion in the System::Data::SqlClient namespace), I am considering to write a separate assembly based on the 2.0 framework and call that function from within the 1.1 main project.

Is such a scenario
* feasible ?
* secure ?
* performance overhead ?

and last, but not least, how to do that? Just build a new 2.0 assembly and reference it within the Visual C++.NET 2003?
Thanks
0pl0
0
0pl0
Asked:
0pl0
  • 2
1 Solution
 
AndyAinscowCommented:
Possibly a silly question but why not have your large project use the .NET 2 framework.  (Anything built to use .net 2 would require it to be installed on the client PC anyway)
0
 
0pl0Author Commented:
That's correct, but Visual Studio 2003.NET Standard does it support a build under the .NET 2.0 framework. In alternative, is it possible (without the syntactical modifications in the managed C++ language (e.g. ^ )) to take the whole project in Visual Studio 2005 Standard and compile it without code modifications under the .NET 2.0 framework?
Thanks
0pl0
0
 
AndyAinscowCommented:
AFAIK the new syntax is optional.
Simplest would be to make a copy of the project and see if it compiles with VS 2005 without (major) problems.  The compiler in VS2005 is stricter - that means some things that would compile under previous versions won't.  The reason for not compiling is not a change is required for changes sake but that the older compiler allowed you to compile potentially dangerous non-standard code.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now