tags:

views:

70

answers:

6

Hi I have to give my customer my application it's a simple application( 3Mo) well I thing it's realy unnecessary to oblige my client to install the hole .NET framework(the 3.5) to work with a simple application ( 3 mo) I mean I'm sure that there is a way to avoid that, Just includ some dlls mybe or something like that Well I have the dll in my project eferance(LINQ dll, core Dll, system Dll, winfom Dll, office Dll and some other) is that possible to give the application with those dll and that whay I avoid installing the hole .NET framework? Well I dont need even to made an MSI or setup project Juste I will give him the exe genrated with the visual studio and that's it

I'm using VS 2010, C#, 3.5.NET

A: 

No it is not possible. Client has to install .NET Framework 3.5 (with SP1) redistributable package.

Edit: If you didn't want client dependency on .NET Framework you should choose another application type: Web application where .NET dependency is only on the server.

Ladislav Mrnka
But why with the Sp1? why not the 3.5 only?
Because when you create application in VS2010 for .NET 3.5 it will use 3.5 SP1.
Ladislav Mrnka
+1  A: 

It's worth noting that Windows comes with various flavours of .Net installed depending on the version of Windows. If I remember correctly...

  • Win7 comes with .NET 3.5 SP1
  • Vista comes with .NET 3.5
  • XP SP2 includes .NET 2

Depending on your target audience you might find that this is good enough!

Dan Puzey
A: 

If are true these conditions:

a) you really want to avoid .NET framework dependency

b) it's a really easy/small application

Consider the option of porting it to c++

If not

use default framework (.NET 2, or 3.5 or 3.5SP1) that comes by default in windows as Dan Puzey said.
cad
If he were going to port it to something else I would recommend Delphi. Yes, it is not dead yet and it would be much easier to move from.
Craig
I choose C++ for the answer because syntax is really similar (less work to do)
cad
A: 

Most people have some flavor of .NET installed although most don't yet have 3.5. But you can create an installer that will download an install transparently to the user. Also if you target the Client Profile this dependency will be smaller.

Craig
A: 

Your client should have .net, there's no reason not to and if they haven't, they are a fool. Running XP with less than Service Pack 2 is dangerous. For the non-technically-inclined, compare it to using a van that's been subject to a manufacturer's recall. It may not necessarily be faulty, but the manufacturer has told you that it's no longer fit for use and are willing to make good at their own expense. As a responsible business owner, you wouldn't shirk that responsibility. In a similar vein, maintaining your Windows installation to the manufacturer's recommendation is not optional.

Tom W
A: 

Thank's all, So I think I have to oblige him to install the 3.5 But I think that MS shoudl finid a way to avoid that, well know we have Win7 with the 3.5 SP1 it's a good Idea but what if we use the 4.0?

Simply you don't understand basics. If you want to write client applications in .NET, your clients must have .NET Framework installed otherwise it will not work. Similar like Java, Java application doesn't work without Java Runtime. There is nothing MS can do with it except offering .NET in updates.
Ladislav Mrnka