Hi Kenneth,

Tried out the new setting, but it did not make any difference.

How did you do that, the setting wasn't implemented in svn trunk until late last night after you posted. Unless you got the code from my sandbox..

So I think this solves the problem.

Sorry, I'm confused what solves what problem? You mean you solved it? Its no longer hidden? Or you just plan to use Chrome?

Best,

Joe

Hi Kenneth,

I can't think of a way to make it easy like with Mono. With Mono we have separate MonoDevelop project files, but in VS we will be using the same project files and references are included in the .csproj file. If we make separate projects and solutions for framework 3.5 it will be a maintenance problem to make sure new files are added to each project.

If you want to zip the 3.5 version dll files and send them to me I'll add them under _libs\net35

but the people who want to use it will have to change the references themselves. If you can outline the basic steps that worked I can add a developer document with those steps.

I'm still a little confused. Is it working for you now with the Tabs enabled or only with them disabled?

Best,

Joe

Ok, so if I understand you correctly, you are saying that though you are able to use the 3.5 framework version of ajaxtoolkit, it doesn't work with ExtJs tabs (the content is hidden if ExtJs tabs are enabled). This is really the main thing I was wanting to find out. More and more I've been having various problems with ExtJs tabs, problems with display in Firefox 3, problems when using an FCKeditor in more than 1 tab. Since the new version of ExtJs has changed the license to GPL, I can no longer upgrade to new versions of ExtJs.

So I'm thinking of switching to YUI tabs everywhere that we are currently using ExtJs tabs. YUI tabs has worked for me in a few places where I've tried it where ExtJs didn't work well. Once I have switched it, you can tell me if it works with the .NET 3.5 version of ajaxtoolkit.

I have added a folder under _libs with the 3.5 versions of ajaxtoolkit and enterprise blocks 4.0. We have not been able to use enterprise block historically due to the license but in the 4.0 release they changed to MsPl license which is compatible. I still can't use it in the core of mojoportal until we change the target runtime to 3.5. Not sure yet when we will do that but it is only a matter of time.

Best,

Joe