.Net Framework 1.1 lifecycle question specific to Windows Server 2003


the .net framework 1.1 made available in downloadable package various operating systems , shipped part of windows server 2003.  meaning, during installation of windows server 2003, .net 1.1 gets installed.

the support lifecycle information .net framework 1.1 states exits support on 10/8/2013.

the support lifecycle information windows server 2003 states exits support on 7/14/2015.

i looking confirmation .net framework 1.1 bits come windows server 2003 continue supported throughout windows server 2003 lifecycle.  cannot imagine ships os would have different lifecycle os itself.

is understanding accurate standalone .net 1.1 package can downloaded , installed on various versions of windows (that not included ie. windows 2003) exits support on 10/8/2013, on windows server 2003, part of windows server 2003, follow windows serer 2003 lifecycle, exists support on 7/14/2015?


armand rouleau

here answer:

we honor lifecycle of underlying .net framework bits bits shipping in os box, if published lifecycle for the .net version happens shorter.

.net 1.1 sp1 shipped in windows server 2003 sp2 x86 (but did not ship in os x64 , ia64), ship 1 patch windows server 2003 sp2 x86 , ship second patch other platforms supported .net 1.1 sp1 customers install stand-alone .net 1.1 redist.

for 2 year period when .net 1.1 sp1 out of extended support windows server 2003 sp2 x86 still in support continue shipping os patch stop shipping second (msi) patch redist. customers running windows server 2003 sp2 x86 still supported .net 11. sp1 security issues entirety of os lifecycle, .net 1.1 sp1 standalone product not supported after 10/8/2013 on platforms bits did not ship in os.


armand rouleau



Windows Server  >  Windows Server General Forum



Comments

Popular posts from this blog

2008 Windows Deployment Server Properties Error

Can no longer user MS Update - Files required to use Microsoft Update are no longer registered

How do a find data in one file, search for it in another file and if not found, write a custom message to another file