.net and coldfusion 8u1
CyberAngel
Ok I am going to say this applies to update 1 of coldfusion at the moment, but may apply to Coldfusion 8 as well.
I have .Net 3.5 installed on my machine at the moment, and trying to get a class library to run in Coldfusion 8. However Coldfusion only wants to see that I have .Net V2.0 installed and ignores the fact that I have both 3.0 and 3.5 installed.
I have this class library that works on the server at work, but will not work on this machine. I assumed it is because it is being compiled to .Net 3.5 and adjusted it to compile to .Net 2.0 with no success.
After reading some notes at adobe, it says that if a new version of .Net runtime is installed you need to reinstall the Coldfusion .Net integrated service. Yet it only picks up that the system is running .Net 2.0;-)
So does anyone have any experience or KB’s or anything that may point to something that can fix or help here?
Andrew.
charlie arehart
Good catch, Andrew. As for “something that can fix”, it seems worth noting that the .NET integration is indeed separately installed from CF, so it seems you don’t need to reinstall all of CF. Can’t tell if you already knew that, so sorry if it’s not the useful info you were looking for. You mention having looked at some “notes at Adobe”. Can’t tell, also, if you’re saying you saw the page on this in the livedocs:
http://livedocs.adobe.com/coldfusion/8/htmldocs/help.html?content=othertechnologies_10.html
It explains how you should be able to uninstall just the .NET service, though it refers to it as the “Adobe Scorpio .NET Service”. I just filed a comment pointing that out. Also, even though I DID have the .NET service installed and running, I did NOT see any listing of the feature in the add/remove programs feature in Control Panel (now called “programs and features” in Vista). I tried to use the uninstall option for CF8 itself, hoping it might offer it as an option perhaps, but instead it did indeed just uninstall all of CF. Doh! I mentioned all that in the comment as well (which won’t likely be there if one looks in the next few hours after I write this).
But I did just notice (too late for me) that the bottom of the page also lists a specific uninstaller exe. Have you tried those yet, Andrew? It seems it may be pretty straightforward doing the uninstall/reinstall. Let us know how that goes for you.
/charlie
Andrew Scott
Yes thats how I knew it was only picking up the .Net 2.0:-)
Not sure about that page you sent me, are you indicating that I should
uninstall the .Net integration service then reinstall?
I will point out that .Net 3.5 has been on this machine before I
installed the 64bit version of Coldfusion to begin with, so I would be
under the assumption that .Net 3.5 should have been picked up.
However if I here you, let me try uninstalling the Coldfusion .Net
service and reinstall. But I have a feeling it is not going to be the
solution. Have to wait and see.
Andrew.
Andrew Scott
Uninstalled and reinstalled and it says .Net 2.0 in the install script.
So something is not right.
--
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 8676 4223
Mobile: 0404 998 273
Andrew Scott
Ok here is something even worse.
<cfobject type=".NET" name="seClass" class="System.Environment">
<cfoutput>#seClass.Get_Version().ToString()#</cfoutput>
I ran this on a server here, and got 1.1.4322.2407J
Yet I know for a fact that this server is not only running 1.1, but it has 2.0sp1, 3.0sp1 and 3.5
So no .net assemblies 2.0 and up will ever work in Coldfusion. I removed the .Net integration services and reinstalled, again the install script only picks up that I have 1.1
Should I be loosing my hair about now?
Andrew Scott
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
style='font-size:12.0pt;font-family:"Times New Roman","serif"'>
charlie arehart
Andrew, I understand your frustration. I’ve not done enough work with the CF/.NET integration to recognize your problem, but I’m not sure you want to conclude, “So no .net assemblies 2.0 and up will ever work in Coldfusion.”, or at least you don’t want to assert that that’s the case for everyone. Surely we’d have heard more of a hue and cry from the community if that were so.
In fact, the CF docs offer an example (in the .NET integration section) that says it’s using a .NET 2.0 class. I’ve tried it myself (the first piece of code) and it worked. What do you find?
http://livedocs.adobe.com/coldfusion/8/htmldocs/help.html?content=dotNet_07.html
Also, the last example on this page also says it’s using a .NET 2.0 only class:
http://livedocs.adobe.com/coldfusion/8/htmldocs/help.html?content=dotNet_07.html
How does that work for you? It worked fine for me. If they work, then clearly (if the docs are to be believed), you can call .NET 2.0 classes.
As for why your call to that system.environment class reported 1.1, I can’t say, but I can say that there could be a lot of possible explanations for what you’re seeing (if the above work), from my experience working with .NET a couple of years ago. Things aren’t quite always what they seem.
Hope that’s helpful. If you continue to experience frustration, how about bringing this up on the Adobe CF forums (advanced techniques or general discussion). There are often people there who have had the same experiences, and who may be able to point you in a better direction to solve the challenge.
/charlie
CyberAngel
Charlie,
Read it in its context, maybe should have chose my words better. I meant that on that server, no .Net 2.0 assemblies will run on Coldfusion.
Charlie, I posted that code in my last post that’s how I know the server is using .Net 1.1 and is not using the .Net 3.5.
Ok for fuck sake let me be very blunt here Charlie.
1) I first posted with it only sees .Net 2.0 on one machine, and it will NOT run .Net 3.5 assemblies.
2) Another machine only ever sees .Net 1.1, so it WILL NOT run .Net 2.0 assemblies.
Do you not keep up with the conversation?
When you have reread my posts, then maybe you can come back and help me out. Till then I did not say Coldfusion could not run .Net 2.0 assemblies. I first stated it would not run .Net 3.5 assemblies. On another machine it will not run .Net 2.0 assemblies because it only sees it having .Net 1.1 and NOT .Net 3.5
How much clearer do I need to make it?
And you wonder why I lose my temper with people for god sake.
CyberAngel
Sorry.
Let me recap again.
Accordingly the machine with .Net 1.1 and .Net 3.5 I have no problems running .Net 2.0 assemblies with other applications that are aware of the .Net 3.5
The point that I was making is that Coldfusion DOES NOT SEE .Net 3.5 and only sees .Net 1.1 so there is no way it will run .Net 2.0 assemblies. That was the point I was making.
Now that we have Coldfusion 8.01 I was clearly told when in the beta program of Coldfusion 8 that it would be aware of .Net 3.0+, I guess I was lied too. And which is why I can’t vouch for Coldfusion 8 only 8.01J
Andrew.
Who is frustrated because people don’t listen properly.
Steve Onnis
Joel Cass
Are you sure that the problem is with CF? Perhaps your .net connector is not configured.
Open the jnbproxy.exe.config file under wherever your connector service is installed (eg. C:\ColdFusion8DotNetService).
You *need* to have the supported runtimes listed, ie this the jnbproxy.exe.config on my comp:
<?xml version="1.0"?>
<configuration>
<startup>
<supportedRuntime version="v2.0.50727"/>
<supportedRuntime version="v2.0.50215"/>
<supportedRuntime version="v1.1.4322"/>
<supportedRuntime version="v1.0.3705"/>
<requiredRuntime version="v1.0.3705"/>
</startup>
…
<configuration>
When I access System.Environment.Version I am getting v2.0.50727.1433
CyberAngel
Steve.
Point taken.
<BR
CyberAngel
Joel,
Thanks but if you followed the thread, I stated that the machine that is coming up as .Net 1.1 DOES NOT have .Net 2.0 installed. It has .Net 3.5 installed.
Coldfusion when it installed DID NOT pick that fact up, and said that I can only find .Net 1.1 installed.
And yes I followed the link that Charlie provided, and had read it many times. Even to the point of me asking maybe I should uninstall it first and then reinstall. But when reinstalling the JnBridge proxy it only picks up .Net 1.1 and states that in the install script.
Secondly, the machine that actually has .Net 2.0 installed is being correctly found. BUT, it also has .Net 3.5 and it IS NOT being found.
Does that make the problem a little more clearer, I appreciate the info, but it doesn’t help when the installer DOESN’T understand what .Net 3.5 is now does it?
The point I am trying to establish here is this, I shouldn’t have to have .Net 2.0 installed for Coldfusion. I should be able to use either the .Net 3.0 or .Net 3.5 framework. However coldfusion as I am now saying for the tenth time WILL NOT acknowledge .Net 3.0 / .Net 3.5
From: cfau...@googlegroups.com
[mailto:cfau...@googlegroups.com] On Behalf Of Joel Cass
Sent: Friday, 18 April 2008 1:30 PM
To: cfau...@googlegroups.com
Subject: [cfaussie] Re: .net and coldfusion 8u1
Are you sure that the problem is with CF? Perhaps your .net connector is not configured.
Joel Cass
OK. What I want to know exactly is whether you have the version number for 3.5 in your config file or not. If not, add it, restart the service, and check if it’s working.
Macromedia/Adobe have a shoddy record for installers so don’t expect the installer to do *anything* for you. What you are talking about is configurable.
If 3.5 is not working after adding it as a supported version, contact someone at adobe (good luck) or check other lists. It’s obvious that we cannot help you.
CyberAngel
Joel…
I tried it, for both .Net 3.0 and 3.5 to no avail.
charlie arehart
Andrew, I read your post, and the entire thread. I really do try to be careful and helpful in my posts, and I’m sorry that my attempts to help just continue to frustrate you. You needn’t worry about it happening again, really.
/charlie
From: cfau...@googlegroups.com
[mailto:cfau...@googlegroups.com] On Behalf Of CyberAngel
Sent: Thursday, April 17, 2008 10:28 PM
To: cfau...@googlegroups.com
Subject: [cfaussie] Re: .net and coldfusion 8u1
Charlie,
rup...@gmail.com
Did you try
1) uninstall CF .NET service
2) Restart the machine
3) install CF .NET service
In the microsoft world, restarting the machine can do wonders ;-)
On a serious note, we did not find any issue during our QA when we ran
in on .NET 3.0 and things worked perfectly. Is it 64-bit .NET by any
chance? I am not sure but may be that can cause some problem here. Let
me give it a try and would let you know my findings.
Rupesh
CyberAngel
Thanks for the response, no I did not try restarting the machine.
As I didn't install the framework, I didn't think of that.
But yes I did uninstall the .Net service and reinstall.
And yes this is the 64 bit version.
-----Original Message-----
From: cfau...@googlegroups.com [mailto:cfau...@googlegroups.com] On Behalf
Of rup...@gmail.com
Sent: Tuesday, 22 April 2008 2:54 AM
To: cfaussie
Subject: [cfaussie] Re: .net and coldfusion 8u1
Andrew Scott
2 running 32 bit OS, which is Vista and Windows 2003 Server. The other is 64
bit and is Vista Ultimate.
I still can't vouch if this is an update 1 problem or it also exists in the
Standard 8 install.
While I am here, I also have another assembly that is partially working. On
32bit systems it works 100%, on 64bit systems it seems to fail at certain
points. I have compiled the code for any cpu, x64, x32 and it doesn't seem
to care. I can use the class on that same machine inside a .Net application
fine, but in Coldfusion it throws an exception. Very weird.
I am talking to the developers of that package, that my wrapper is for. But
I am also wondering if it might be something to do with Coldfusion on 64bit,
as it work on 32 bit systems fine?
I have tried every combination of compiles here, compile on 32bit, compile
on 64 bit, compile on both with any cpu, or x64, or x32 with the same
results.
Seeing as the assembly referenced in my class works inside of a normal .Net
application running the same assembly reference I am thinking that it is a
Coldfusion issue myself.
Andrew Scott
Senior Coldfusion Developer
Aegeon Pty. Ltd.
www.aegeon.com.au
Phone: +613 9015 8628
Mobile: 0404 998 273