Could installing .NET version 4.6 on Windows Server 2008 cause any issues? - .net

I am installing a web service on a client's server. This .NET service is compiled in version 4.6.1. The client's server (Windows 2008 R2) does not have .NET version installed to this level.
The client is worried that by installing this upgrade, it will cause conflicts with other software on this server. (it is a production server, they are a financial institution and there are various financial programs and databases stored there).
I have upgraded several other machines with .NET Framework updates and never had an issue. I have tried to research potential pitfalls on the internet but could not find any.
Does anyone have precautions to suggest, or on the other hand, any assurances I can pass along to this client?


Could not create the driver from NHibernate.Driver.OracleDataClientDriver Version=4.030319

I have been battling with this for last few days and I am at my wits end!
My project have moved to a new development environment coming from Server 2008 to Server 2016. The application uses .Net Framework 4.0, Oracle Client win32_11gR2 and NHibernate 4.030319. Now of course this all works wonderfully on Server 2008 R2, but on Server 2016, we are not able to get things to work.
Whilst I do appreciate that the 11g version of Oracle needs .Net Framework 3.5 to be installed, but because we are not in charge of the actual operating system this is under control of our support guys, we tried the 12c version of the client. This installed ok, but when we tried calling the application, it errored with "Could not create the driver from NHibernate.Driver.OracleDataClientDriver".
I have tried putting in the machine.config setting for Database Factories, but nothing seems to make this work since moving to Server 2016.
Does anyone know how to get this to work on Windows Server 2016?
It will work after getting the .Net Framework 3.5 installed via add features. For my benefit it will work with the 64 bit version. Ignore during the installation the message that says that your environment does not meet minimum requirements.

Upgrading OS Server after installing applications

I have installed certain applications in my VM which has Windows OS Server 2008. Now, If I upgrade the Windows Server to 2012, will it affect my applications in anyway?
I could see that the application is supported in 2012 Server.
It really depends on the applications, but most should be fine. I would recommend taking a snapshot of your old installation so that you can quickly go back to WS 2008 if need be.
Check with application vendor if they support 2012 version OS. Don't upgrade the instance without a snapshot. Most applications should work, unless any App-OS dependency.

Did VB 6/.NET interop recently get broken by a Windows update?

Recently a VB 6 application using .NET 1.1/2.0 components stopped working on my companies XP machines. The IT department was installing Windows patches at the time, so I'm wondering if anyone has heard of an update breaking VB 6/.NET interop?
Are you running the COM+ components as proxies against other servers? If so, I've had problems before when installing e.g. SP2 for Windows 2003 server, in that the COM+ settings (Component Services, root node) have had the "remote activation" security setting permission missing after the update. Don't know if this is your problem, though.

Is Enterprise Library 4.1 and server 2008 sp2 compatible? I can't find specifics on this

What I thought would be an easy google turned up no results. I'm trying to find out if Enterprise Library 4.1 is compatible with Windows Server 2008 SP2.
The system requirements say its compatible with Server 2008, but there is no mention of the service pack. Does anyone know definitively if these two are compatible?
Thank you for your time.
Typically compatibilities will list the minimum requirements; compatible with "Windows Server 2008" would include it and subsequent service packs (unless explicitly indicated otherwise). Keep in mind EL 4.1 was released almost a year before 2k8 SP2 was.
Does anyone know definitively if these two are compatible?
I guess it would depend on how you define "definitively" and "compatible". ;)
Do you want to know if Enterprise Library will run under Windows 2008 Server SP2? I don't believe that it was formally tested against that version (typically testing will go back two OS releases and SP2 didn't come out until the year after Enterprise Library was released) but it should work on later OS versions. For example, I have used version 4.1 with Windows 7.

Backward Compatibility in Windows Forms App built on .NET 4

I have built an application using c# on .NET. My software will run on PCs having XP SP3 to Win 7. I did my research in deciding which version of .NET to use for development. Microsoft website clearly says that .NET 4 apps can run on XP SP3. I trusted them, built the app till a month where its halfway, I just had a test deployment & boooooom. Its not even starting up & gives errors that not all components required are installed. I researched and SQL Server 2008 couldnt be installed.
I've done the following:
- Tried to install .NET 4 on XP SP3. Gets installed easily. BUT SQL Server express 2008 (which my app uses) couldnt be installed, it says to install .NET 2
- IF I install .NET 2, I am not sure whether the app will run on Windows 7.
Please Help. My Client will kill me !
.NET 2.0 and .NET 4.0 will run side by side without an issue. In fact, Windows 7 comes preinstalled with .NET 2.0, though you may need to enable it manually.
You may want to post a more detailed question with your errors, as there shouldn't be any insurmountable problems with any of what you're trying to do. SQL Server 2008 Express, for instance, should work fine on XP SP3.
Application written for NET 2.0 works fine in Windows7.
But, instead of downgrading the framework library, I think you should check if your app really requires SqlServer 2008.
Perhaps you could simply downgrade to use SqlServer Express 2005 and recreate your database.
This will be less limiting from the point of view of your coding possibilities.