Is it possible to use a c# dll in an environment where the dot net framework has not been installed ?

For example will a C++ wrapper do the job?

Thanks.
DD

Hi Dave,

No. You need .net environment to execute .net code.

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

"Dave52" <(E-Mail Removed)> wrote in message
news:09F50033-405C-41AE-972B-(E-Mail Removed)...
> Is it possible to use a c# dll in an environment where the dot net
framework has not been installed ?
>
> For example will a C++ wrapper do the job?
>
> Thanks.
> DD

It's possible if you use our linker tool:

http://www.remotesoft.com/linker/

It will include a subset of the framework along with your C# dll and a
native stub for that dll.

For instance, you could use the tool to write an Office .NET addin, and a
..NET windows forms user control for IE, and deploy them w/o the full .NET
framework.

"Dave52" <(E-Mail Removed)> wrote in message
news:09F50033-405C-41AE-972B-(E-Mail Removed)...
> Is it possible to use a c# dll in an environment where the dot net
framework has not been installed ?
>
> For example will a C++ wrapper do the job?
>
> Thanks.
> DD

Hi,

The product seems interesting and I might even use it in one future project.
However, I guess you loose some functionality, such as loading external
assemblies, security isn't fully enabled I guess, ....
Do you have a list of drawbacks?

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

"remotesoft" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> It's possible if you use our linker tool:
>
> http://www.remotesoft.com/linker/
>
> It will include a subset of the framework along with your C# dll and a
> native stub for that dll.
>
> For instance, you could use the tool to write an Office .NET addin, and a
> .NET windows forms user control for IE, and deploy them w/o the full .NET
> framework.
>
> "Dave52" <(E-Mail Removed)> wrote in message
> news:09F50033-405C-41AE-972B-(E-Mail Removed)...
> > Is it possible to use a c# dll in an environment where the dot net
> framework has not been installed ?
> >
> > For example will a C++ wrapper do the job?
> >
> > Thanks.
> > DD
>
>

> Do you have a list of drawbacks?

First drawback i see is that it increase the filesize of your
application.....

--
LEBRUN Thomas
http://morpheus.developpez.com


"Miha Markic [MVP C#]" <miha at rthand com> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> The product seems interesting and I might even use it in one future
project.
> However, I guess you loose some functionality, such as loading external
> assemblies, security isn't fully enabled I guess, ....
> Do you have a list of drawbacks?
>
> --
> Miha Markic [MVP C#] - RightHand .NET consulting & development
> miha at rthand com
> www.rthand.com
>
> "remotesoft" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > It's possible if you use our linker tool:
> >
> > http://www.remotesoft.com/linker/
> >
> > It will include a subset of the framework along with your C# dll and a
> > native stub for that dll.
> >
> > For instance, you could use the tool to write an Office .NET addin, and
a
> > .NET windows forms user control for IE, and deploy them w/o the full
..NET
> > framework.
> >
> > "Dave52" <(E-Mail Removed)> wrote in message
> > news:09F50033-405C-41AE-972B-(E-Mail Removed)...
> > > Is it possible to use a c# dll in an environment where the dot net
> > framework has not been installed ?
> > >
> > > For example will a C++ wrapper do the job?
> > >
> > > Thanks.
> > > DD
> >
> >
>
>

"Lebrun Thomas" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> > Do you have a list of drawbacks?
>
> First drawback i see is that it increase the filesize of your
> application.....


:-). A big one I guess.
However, sometimes it doesn't matter, for example if you are producing some
sort of a CD catalog application.

--
Miha Markic [MVP C#] - RightHand .NET consulting & development
miha at rthand com
www.rthand.com

> However, sometimes it doesn't matter, for example if you are producing
some
> sort of a CD catalog application.

Yes, i know. But as you said, sometimes it doesn't matter, not always

Bye.

--
LEBRUN Thomas
http://morpheus.developpez.com


"Miha Markic [MVP C#]" <miha at rthand com> wrote in message
news:(E-Mail Removed)...
>
> "Lebrun Thomas" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > > Do you have a list of drawbacks?
> >
> > First drawback i see is that it increase the filesize of your
> > application.....
>
>
> :-). A big one I guess.
> However, sometimes it doesn't matter, for example if you are producing
some
> sort of a CD catalog application.
>
> --
> Miha Markic [MVP C#] - RightHand .NET consulting & development
> miha at rthand com
> www.rthand.com
>
>

Thanks for your interest in our products.

No, it does not loose any functionality, rather it retains all features of
the original application, including dynamic loading of external assemblies
(don't link such assemblies, and make sure all dependencies are
mini-deployed). The big difference is that .NET Framework is now a part of
your own applications, so the user doesn't really see the Framework in the
picture, and therefore, it may not be convenient if you want to do something
to the framrwork as a whole, such as running the Framework configuration
utility. Framework utilities are not deployed with the application. All
configurations are done at development time, so when the app ships, it
contains an isolated and much smaller version of the framework, which is
internal to the mini-deployed applications. Even when a full framework
exists on the same machine, the mini-deployed app wouldn't know it at all,
which is quite useful considering the many difference versions and service
packs of the framework yet to come.

The mini-deployed applications has all security features of the original
..NET app. In the case of a managed user control under IE, there is a little
difference in the HTML that deployes the control. When full .NET framework
exists, you can use the extended <object> tag to embed the control, however
when mini-deployed, it rolls back to the regular scenario of a traditional
ActiveX control.

I guess a mjor difference also lays in terms of upgrades. When a
mini-deployed app needs to a new version of the framework, you need to
re-generate the mini-package to contain the latest subset of the framework.

"Miha Markic [MVP C#]" <miha at rthand com> wrote in message
news:(E-Mail Removed)...
> Hi,
>
> The product seems interesting and I might even use it in one future
project.
> However, I guess you loose some functionality, such as loading external
> assemblies, security isn't fully enabled I guess, ....
> Do you have a list of drawbacks?
>
> --
> Miha Markic [MVP C#] - RightHand .NET consulting & development
> miha at rthand com
> www.rthand.com
>
> "remotesoft" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > It's possible if you use our linker tool:
> >
> > http://www.remotesoft.com/linker/
> >
> > It will include a subset of the framework along with your C# dll and a
> > native stub for that dll.
> >
> > For instance, you could use the tool to write an Office .NET addin, and
a
> > .NET windows forms user control for IE, and deploy them w/o the full
..NET
> > framework.
> >
> > "Dave52" <(E-Mail Removed)> wrote in message
> > news:09F50033-405C-41AE-972B-(E-Mail Removed)...
> > > Is it possible to use a c# dll in an environment where the dot net
> > framework has not been installed ?
> > >
> > > For example will a C++ wrapper do the job?
> > >
> > > Thanks.
> > > DD
> >
> >
>
>