This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Install Shield searching .Net 3.5 Features on Server 2012
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 27, 2013
02:00 AM
Install Shield searching .Net 3.5 Features on Server 2012
Hello,
I am creating install script project using Install shield 2009, this setup is working correctly in all OS, but for server 2012, It is installing the setup well, but at the last it is searching for Windows default feature and giving this warning The fallowing feature couldn't be installed, .Net Framework 3.5 , As I don't need this feature, My project is in Java, I didn't keep any .Net dependencies or prerequisite in project, Then Why it is searching this feature at last of setup,:confused:
Help me out this problem
I am creating install script project using Install shield 2009, this setup is working correctly in all OS, but for server 2012, It is installing the setup well, but at the last it is searching for Windows default feature and giving this warning The fallowing feature couldn't be installed, .Net Framework 3.5 , As I don't need this feature, My project is in Java, I didn't keep any .Net dependencies or prerequisite in project, Then Why it is searching this feature at last of setup,:confused:
Help me out this problem
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 30, 2013
05:24 AM
Nobdy Knws!!!!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 30, 2013
10:07 AM
Windows 8 and Server 2012 have a new OS "feature" in which they will pop up that dialog in the middle of a any other setup, if the OS thinks that a .Net file of some kind has been installed. Microsoft thinks this is a create idea but it causes lots of grief. So to debug this situation I would selectively eliminate Components and Features from my setup to isolate which file Windows Server 2012 is thinking needs .Net support. Alternatively if you can't figure out what is triggering the OS to think that there is a .Net dependency you could call DISM to enable the NetFx3 feature.