This project has moved and is read-only. For the latest updates, please go here.

.NET Framework 3.5 only on SOE

May 16, 2012 at 9:43 AM
Edited May 16, 2012 at 9:43 AM

Hi, this programs rocks and is the only one I could find that could handle my multi-line requirement for some replacement text! Thank you :)

When I actually tested it on my target machines, I find they doesn't meet fnr's .NET requirement. I'm unable to get .NET 4 installed on these machines, as they are locked down to the Standard Operating Environment set by our company. They do have .NET 3.5 installed though.

Might you have a copy of fnr.exe that will run under .NET 3.5 framework please?





May 16, 2012 at 10:00 AM
Edited May 16, 2012 at 10:00 AM


I rebuilt the fnr.exe with target framework 3.5.

Can you try downloading from here:


Let me know if it works.


May 17, 2012 at 6:25 AM

Thanks for your effort Eric!

I tried that new exe, but unfortunately it still gives me the same error...
fnr.exe - .NET Framework Initialization Error
To run this application, you first must install one of the following versions of the .NET Framework:
Contact your application publisher for instructions about obtaining the appropriate version of the .NET Framework.

I've tried it on two of our PCs with .NET 3.5 installed, but the message is identical, regardless of which exe I run.

Anything else I should try ?

May 18, 2012 at 12:20 PM
Edited May 18, 2012 at 12:21 PM

The new exe (which I renamed to fnr(3.5).exe to differentiate between the two version) of course runs fine on different PC with .NET 4 installed.

I just checked out its properties in Process Explorer and it reports the following...
fnr(3.5).exe:11808 Properties
Image | Performance | Disk and Network | Performance Graph | Threads | TCP/IP | Security | Environment | Job | .NET Assemblies | .NET Performance | Strings |
Structure                                    Flags                                      Path
-CLR v4.0.30319.1                        ConcurrentGC, ManagedExe
   -Appdomain: SharedDomain     Shared
      mscorlib                               DomainNeutral, Native             C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mscorlib\bc19222db4406c472d9aa1f8b6e0f470\

   -Appdomain: fnr(3.5).exe           Default, Executable
      fnr2                                                                                    C:\~~tmp\fnr(3.5).exe
      System                                  Native                                     C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System\0f8f78b729ce16dd078f5d5f734a1110\
      System.Drawing                     Native                                     C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Drawing\1266d26c7b7843d308e2705cb8239d55\
      System.Windows.Forms          Native                                     C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\f0acb5c0e7dc2c42c6c61f3aa1278338\

Is this information of any help to you?

May 21, 2012 at 10:55 AM

FYI, I only added the above info, becasue i thought it was odd to see v4.0.3..  amongst what Process Explorer was reporting about the new exe, if it was meant to run on the v3.5 Framework.

Is compiling/rebuilding to use .NET 3.5 something I can attempt using your source code?

I'm not a developer at all so not really sure where to start, but would still really like to use this app.

May 30, 2012 at 8:45 AM

Oh well, thanks for trying, guess I'm on my own from here.

May 30, 2012 at 9:37 AM
Edited May 30, 2012 at 9:37 AM


I made a mistake in original 3.5 exe.  I recompiled the fnr application correctly in .NET 3.5, but as a final step I used ILMerge to combine:




and several other dlls into one exe.


ILMerge has a switch /target:4,   so it merged the exe and DLLs in .NET 4.   I changed it to /target:2, which should now work in .NET 3.5.

I checked it in Process Explorer and all dependencies are now in .NET 2.0...

Try it out and let me know.

The new file is:


May 31, 2012 at 6:50 AM
Edited May 31, 2012 at 6:51 AM

Eric, you are a champion... It's working beautifully now on my target machines. THANK YOU!!!!

Without rambling too much, I've had a very stressful couple of weeks, and I just wanted to say, your efforts to assist me here have really made my day!

Also, just general kudos on your great approach to a simple and powerful text replacement tool! :)