|
-
Jun 18th, 2010, 12:36 PM
#1
easiest wat to import .NET 4 fw to windows server 2003
which file i should install in our windows server 2003 for it to support the windows 2003 server should i download the all framework (200+ mb i think) ?
* Rate It  If you Like it
__________________________________________________________________________________________
" Programming is like sex: one mistake and you’re providing support for a lifetime."
Get last SQL insert ID 
-
Jun 18th, 2010, 12:42 PM
#2
Re: easiest wat to import .NET 4 fw to windows server 2003
What else would you install?
-
Jun 18th, 2010, 12:47 PM
#3
Re: easiest wat to import .NET 4 fw to windows server 2003
nothing i only need .NET 4 applications (ASP.NET/windows applications) will be able to run on this machine
* Rate It  If you Like it
__________________________________________________________________________________________
" Programming is like sex: one mistake and you’re providing support for a lifetime."
Get last SQL insert ID 
-
Jun 18th, 2010, 01:32 PM
#4
Re: easiest wat to import .NET 4 fw to windows server 2003
I don't mean what else besides the Framework. You asked:
should i download the all framework (200+ mb i think) ?
and I'm asking, somewhat rhetorically, what the alternatives are. The answer is that there aren't any. You either install the Framework or you don't. There is the client-only profile but you're not running client applications so that's obviously not an option. There are no other options.
-
Jun 18th, 2010, 10:16 PM
#5
Re: easiest wat to import .NET 4 fw to windows server 2003
Hi.
There is also a change that Web service extensions for 4.0 framework not to be created on IIS so you might have to do it yourself.
I don't recall if this happens when you install IIS first and then the framework or the opposite.
ἄνδρα μοι ἔννεπε, μοῦσα, πολύτροπον, ὃς μάλα πολλὰ
πλάγχθη, ἐπεὶ Τροίης ἱερὸν πτολίεθρον ἔπερσεν·
-
Jun 19th, 2010, 03:39 PM
#6
Re: easiest wat to import .NET 4 fw to windows server 2003
 Originally Posted by jmcilhinney
I don't mean what else besides the Framework. You asked:and I'm asking, somewhat rhetorically, what the alternatives are. The answer is that there aren't any. You either install the Framework or you don't. There is the client-only profile but you're not running client applications so that's obviously not an option. There are no other options.
If someone says they just need to be able to run winforms and ASP.NET apps then I would say the client profile would be fine - but it depends what they mean by "run". If you actually want to host the ASP.NET apps on that server then no the client profile will not be ok, but if you just want to access web pages that use ASP.NET then its fine because you dont even need any version of the .NET framework to be able to access an ASP.NET website as all the .NET stuff is done on the server side.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|