Jiffycms wysiwyg rich text HTML editor for ASP.NET AJAX

Closed Issue: Text is duplicated after a spellcheck. [4474]

jiffycms — Thu, 28 Jan 2010 19:05:21 GMT

Using the online demo.

1) select the image browser demo.
2) click the spell checker. Select any dictionary.

Your text is now duplicated.

I beleive this has something to do with the PostbackAllFormData="True" as that is the only demo that this occurs on.
Comments:

Closed Issue: Error: g is null in the HTML Editor [5050]

jiffycms — Thu, 28 Jan 2010 19:04:41 GMT

Hi All,

I just started using the JiffyCMS controls ,v1.0.9.9, when i faced this problem.
Every time i click on the HTML Editor control or when it loads on the page i get this error
"Error: g is null
Source File: http://localhost:23322/JiffycmsToolkitExamplesV1.0.9.9/WebResource.axd?d=XVApzw21tgvOyBVwYKBc1rMXcV5Y0KBt03vXLkiyoNNvEl0uUjeQfkH5tarQ17YMHYBJdst6VLwOjNYTb4UQfnfQmurcP0nSJH6ksnG4rgfvRWPPT-swK2Xwlwjz16ZG0&t=633975147160000000
Line: 1"

which of course is causing me alot of trouble since it reloads the whole page with postback.

I'm using VS2008 and my project is framework 3.5

can anyone please tell me whats wrong?

Thank you
Comments:

This needs to be reported on our forum. (we are not using the issue tracker on codeplex). If I'm not mistaken we have already dealth with this and fixed it. If otherwise, report it on the forum again. Thank you.

Closed Issue: Spell Checker Not Working [4646]

jiffycms — Thu, 28 Jan 2010 19:02:37 GMT

The spell checker appears to delete any new text entered into the editor, and does not highlight misspelled words as the popup instructions indicate.
Comments:

This needs to be posted on our forum (we are not using the Issue tracker on codeplex) and indeed someone had already taken the time to report it. This problem has already been fixed long ago. Thanks to all who reported.

Closed Issue: Html Editor does not work with TabContainer [5096]

jiffycms — Thu, 28 Jan 2010 19:00:25 GMT

I work with the Ajax Control Toolkit, in VS2005, and use in my project theTabControl.

If i put an Editor in a TabPanel and this is the ActivePanel the Editor works ok, but if a put an Editor control in a TabPanel that isn't the ActivePanel it shows like the attached image.
Comments:

This needs to be posted on our forum. We are not using the Issue tracker on codeplex. Chadboettcher has already reported this on the forum(thank you chad). It will be fixed in the coming release.

Updated Wiki: Home

jiffycms — Sat, 23 Jan 2010 10:51:34 GMT

Project Description
Jiffycms is primarily a wysiwyg ASP.NET rich text HTML editor (RTE), but also contains an image picker control, image gallery, media frame (a sort of light box, much more advanced), a color picker and an update progress panel etc. All nicely contained within a single dll...

Online demo http://www.jiffycms.net/demo/default.aspx

Please note that Jiffycms.Net.Toolkit is GPL licensed, which means its free to use while meeting the GPL requirements. If closed source license is more appropriate for your current project, we also offer closed source licensing.
You may check out our closed source licenses here : http://www.jiffycms.net/closedsource.aspx

For screenshots, scroll to the bottom of the page :-)

Update: 09/01/2010 jiffycms is now on twitter http://twitter.com/jiffycms. This is the fastest way to know all the latest fixes and what's going on. You are encouraged to subscribe to stay ontop of things.

Installation Requirements :

The control will work in Visual studio 2008 (our current development environment) and should work nicely under Visual studio 2005 ; The express editions of both 2k8 and 2k5 should work nicely too. Just make sure you have installed .NET 3.5 (specifically, the control references System.Web.Extensions Version 3.5 dll which is currently provided in the .NET 3.5 install; Reference for details : http://weblogs.asp.net/scottgu/archive/2007/07/30/asp-net-ajax-in-net-3-5-and-vs-2008.aspx

There is no special requirement for vs2k5 ; All editions of VS2k5 including express are able to run ASP.NET 2.0 applications and .NET 3.5 is simply an upgrade of extra extention dlls, nothing more. So make sure you have .NET 3.5 installed. One thing to note here is that you won't be able to use any new additions in .NET 3.5 that require compiler support such as linq,wcf, wpf etc, all things that jiffycms has no dependency on and you should be fine. Make sure you meet this requirement.

Simple howto- For Visual Studio 2005 development environment users :

You may try adding an assembly redirect in your current web.config file. You can do this in two ways, first, you can try by redirecting all bindings to System.Web.Extentions 3.5 (the latest version the editor is built on) to go to your current version in use (the older one).

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="3.5.0.0" newVersion="1.0.61025.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

note the oldversion and the new version? It basically takes any requests for 3.5 version and redirects to the older one that you are currently using.
This is supposedly the easiest way to get things rolling for you.

If the above doesn't work, here's a second method :

Another approach is to download and get the System.Web.Extentions 3.5 assembly. Then reference this assembly in your project manually. Finally add an assembly redirect to it in web.config like this :

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

Lastly, experiment with method 1 and 2 above, there is no perfect solution for VS2k5 users unfortunately.

Registering the custom httpHandler :

The toolkit requires that you add configuration settings to an httphandler in your web.config file. You can get the toolkit to register the handler automatically by dragging and dropping the control from the toolbox to the designer surface. A second option is to register the handler manually in web.config as follows :

add the following entry under the path Configuration/httpHandlers section for IIS6 :

<add verb="*" path="jiffycms.axd" type="Jiffycms.Net.Toolkit.WebResourceHandler" />

For IIS7, you need to make an entry under the path : Configuration/system.webServer/Handlers section as follows :

<add verb="*" path="jiffycms.axd" name="WebResourceHandler"
type="Jiffycms.Net.Toolkit.WebResourceHandler"
preCondition="integratedMode" />

for details, reference the following article :

http://www.jiffycms.net/Article/htmleditor-tutorials/23/Using-an-External-StyleSheet-with.aspx

If you need help, post on our forum http://www.jiffycms.net/forum/default.aspx

Quick start introduction tutorials
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/19/23/Using-an-External-StyleSheet-with.aspx
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/22/25/Setting-up-an-image-gallery-in.aspx

A quick preview of designtime features supported in VS.NET
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/16/21/Jiffycms-HTML-Editor-DesignView.aspx

Jiffycms HTML Editor V1.0 Quick links
Project homepage http://www.jiffycms.net/default.aspx
Tutorials http://www.jiffycms.net/article/htmleditor-tutorials.aspx (more coming, be patient)

Blog http://www.jiffycms.net/article/technical-blog.aspx

Post on the support forum below for questions you may have
Support forum http://www.jiffycms.net/forum/default.aspx

screen shots

Easily customize with custom themes you* yourself create easily

Now also supports RTL

More RTL

Inventors of the floating toolbar on an HTML Editor (maximum flexibility) :-)

Basic mode, perfect for blog comments

Updated Wiki: Home

jiffycms — Sat, 23 Jan 2010 10:44:54 GMT

Project Description
Jiffycms is primarily a wysiwyg ASP.NET rich text HTML editor (RTE), but also contains an image picker control, image gallery, media frame (a sort of light box, much more advanced), a color picker and an update progress panel etc. All nicely contained within a single dll...

Online demo http://www.jiffycms.net/demo/default.aspx

Please note that Jiffycms.Net.Toolkit is GPL licensed, which means its free to use while meeting the GPL requirements. If closed source license is more appropriate for your current project, we also offer closed source licensing. You may check out our closed source licenses here :
http://www.jiffycms.net/closedsource.aspx

For screenshots, scroll to the bottom of the page :-)

Update: 09/01/2010 jiffycms is now on twitter http://twitter.com/jiffycms. This is the fastest way to know all the latest fixes and what's going on. You are encouraged to subscribe to stay ontop of things.

Installation Requirements :

The control will work in Visual studio 2008 (our current development environment) and should work nicely under Visual studio 2005 ; The express editions of both 2k8 and 2k5 should work nicely too. Just make sure you have installed .NET 3.5 (specifically, the control references System.Web.Extensions Version 3.5 dll which is currently provided in the .NET 3.5 install; Reference for details : http://weblogs.asp.net/scottgu/archive/2007/07/30/asp-net-ajax-in-net-3-5-and-vs-2008.aspx

There is no special requirement for vs2k5 ; All editions of VS2k5 including express are able to run ASP.NET 2.0 applications and .NET 3.5 is simply an upgrade of extra extention dlls, nothing more. So make sure you have .NET 3.5 installed. One thing to note here is that you won't be able to use any new additions in .NET 3.5 that require compiler support such as linq,wcf, wpf etc, all things that jiffycms has no dependency on and you should be fine. Make sure you meet this requirement.

Simple howto- For Visual Studio 2005 development environment users :

You may try adding an assembly redirect in your current web.config file. You can do this in two ways, first, you can try by redirecting all bindings to System.Web.Extentions 3.5 (the latest version the editor is built on) to go to your current version in use (the older one).

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="3.5.0.0" newVersion="1.0.61025.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

note the oldversion and the new version? It basically takes any requests for 3.5 version and redirects to the older one that you are currently using.
This is supposedly the easiest way to get things rolling for you.

If the above doesn't work, here's a second method :

Another approach is to download and get the System.Web.Extentions 3.5 assembly. Then reference this assembly in your project manually. Finally add an assembly redirect to it in web.config like this :

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

Lastly, experiment with method 1 and 2 above, there is no perfect solution for VS2k5 users unfortunately.

Registering the custom httpHandler :

The toolkit requires that you add configuration settings to an httphandler in your web.config file. You can get the toolkit to register the handler automatically by dragging and dropping the control from the toolbox to the designer surface. A second option is to register the handler manually in web.config as follows :

add the following entry under the path Configuration/httpHandlers section for IIS6 :

<add verb="*" path="jiffycms.axd" type="Jiffycms.Net.Toolkit.WebResourceHandler" />

For IIS7, you need to make an entry under the path : Configuration/system.webServer/Handlers section as follows :

<add verb="*" path="jiffycms.axd" name="WebResourceHandler"
type="Jiffycms.Net.Toolkit.WebResourceHandler"
preCondition="integratedMode" />

for details, reference the following article :

http://www.jiffycms.net/Article/htmleditor-tutorials/23/Using-an-External-StyleSheet-with.aspx

If you need help, post on our forum http://www.jiffycms.net/forum/default.aspx

Quick start introduction tutorials
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/19/23/Using-an-External-StyleSheet-with.aspx
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/22/25/Setting-up-an-image-gallery-in.aspx

A quick preview of designtime features supported in VS.NET
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/16/21/Jiffycms-HTML-Editor-DesignView.aspx

Jiffycms HTML Editor V1.0 Quick links
Project homepage http://www.jiffycms.net/default.aspx
Tutorials http://www.jiffycms.net/article/htmleditor-tutorials.aspx (more coming, be patient)

Blog http://www.jiffycms.net/article/technical-blog.aspx

Post on the support forum below for questions you may have
Support forum http://www.jiffycms.net/forum/default.aspx

screen shots

Easily customize with custom themes you* yourself create easily

Now also supports RTL

More RTL

Inventors of the floating toolbar on an HTML Editor (maximum flexibility) :-)

Basic mode, perfect for blog comments

Updated Wiki: Home

jiffycms — Sat, 23 Jan 2010 10:44:26 GMT

Project Description
Jiffycms is primarily a wysiwyg ASP.NET rich text HTML editor (RTE), but also contains an image picker control, image gallery, media frame (a sort of light box, much more advanced), a color picker and an update progress panel etc. All nicely contained within a single dll...

Online demo http://www.jiffycms.net/demo/default.aspx

Please note that Jiffycms.Net.Toolkit is GPL licensed, which means its free to use while meeting the GPL requirements. If closed source license is more appropriate for your current project, we also offer closed source licensing. You may check out our closed source licenses here : http://www.jiffycms.net/closedsource.aspx

For screenshots, scroll to the bottom of the page :-)

Update: 09/01/2010 jiffycms is now on twitter http://twitter.com/jiffycms. This is the fastest way to know all the latest fixes and what's going on. You are encouraged to subscribe to stay ontop of things.

Installation Requirements :

The control will work in Visual studio 2008 (our current development environment) and should work nicely under Visual studio 2005 ; The express editions of both 2k8 and 2k5 should work nicely too. Just make sure you have installed .NET 3.5 (specifically, the control references System.Web.Extensions Version 3.5 dll which is currently provided in the .NET 3.5 install; Reference for details : http://weblogs.asp.net/scottgu/archive/2007/07/30/asp-net-ajax-in-net-3-5-and-vs-2008.aspx

There is no special requirement for vs2k5 ; All editions of VS2k5 including express are able to run ASP.NET 2.0 applications and .NET 3.5 is simply an upgrade of extra extention dlls, nothing more. So make sure you have .NET 3.5 installed. One thing to note here is that you won't be able to use any new additions in .NET 3.5 that require compiler support such as linq,wcf, wpf etc, all things that jiffycms has no dependency on and you should be fine. Make sure you meet this requirement.

Simple howto- For Visual Studio 2005 development environment users :

You may try adding an assembly redirect in your current web.config file. You can do this in two ways, first, you can try by redirecting all bindings to System.Web.Extentions 3.5 (the latest version the editor is built on) to go to your current version in use (the older one).

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="3.5.0.0" newVersion="1.0.61025.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

note the oldversion and the new version? It basically takes any requests for 3.5 version and redirects to the older one that you are currently using.
This is supposedly the easiest way to get things rolling for you.

If the above doesn't work, here's a second method :

Another approach is to download and get the System.Web.Extentions 3.5 assembly. Then reference this assembly in your project manually. Finally add an assembly redirect to it in web.config like this :

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

Lastly, experiment with method 1 and 2 above, there is no perfect solution for VS2k5 users unfortunately.

Registering the custom httpHandler :

The toolkit requires that you add configuration settings to an httphandler in your web.config file. You can get the toolkit to register the handler automatically by dragging and dropping the control from the toolbox to the designer surface. A second option is to register the handler manually in web.config as follows :

add the following entry under the path Configuration/httpHandlers section for IIS6 :

<add verb="*" path="jiffycms.axd" type="Jiffycms.Net.Toolkit.WebResourceHandler" />

For IIS7, you need to make an entry under the path : Configuration/system.webServer/Handlers section as follows :

<add verb="*" path="jiffycms.axd" name="WebResourceHandler"
type="Jiffycms.Net.Toolkit.WebResourceHandler"
preCondition="integratedMode" />

for details, reference the following article :

http://www.jiffycms.net/Article/htmleditor-tutorials/23/Using-an-External-StyleSheet-with.aspx

If you need help, post on our forum http://www.jiffycms.net/forum/default.aspx

Quick start introduction tutorials
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/19/23/Using-an-External-StyleSheet-with.aspx
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/22/25/Setting-up-an-image-gallery-in.aspx

A quick preview of designtime features supported in VS.NET
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/16/21/Jiffycms-HTML-Editor-DesignView.aspx

Jiffycms HTML Editor V1.0 Quick links
Project homepage http://www.jiffycms.net/default.aspx
Tutorials http://www.jiffycms.net/article/htmleditor-tutorials.aspx (more coming, be patient)

Blog http://www.jiffycms.net/article/technical-blog.aspx

Post on the support forum below for questions you may have
Support forum http://www.jiffycms.net/forum/default.aspx

screen shots

Easily customize with custom themes you* yourself create easily

Now also supports RTL

More RTL

Inventors of the floating toolbar on an HTML Editor (maximum flexibility) :-)

Basic mode, perfect for blog comments

Updated Wiki: Home

jiffycms — Sat, 23 Jan 2010 10:43:58 GMT

Project Description
Jiffycms is primarily a wysiwyg ASP.NET rich text HTML editor (RTE), but also contains an image picker control, image gallery, media frame (a sort of light box, much more advanced), a color picker and an update progress panel etc. All nicely contained within a single dll...

Online demo http://www.jiffycms.net/demo/default.aspx

Please note that Jiffycms.Net.Toolkit is GPL licensed. Which means it's free to use while meeting the GPL requirements. If closed source license is more appropriate for your current project, we also offer closed source licensing. You may check out our closed source licenses here : http://www.jiffycms.net/closedsource.aspx

For screenshots, scroll to the bottom of the page :-)

Update: 09/01/2010 jiffycms is now on twitter http://twitter.com/jiffycms. This is the fastest way to know all the latest fixes and what's going on. You are encouraged to subscribe to stay ontop of things.

Installation Requirements :

The control will work in Visual studio 2008 (our current development environment) and should work nicely under Visual studio 2005 ; The express editions of both 2k8 and 2k5 should work nicely too. Just make sure you have installed .NET 3.5 (specifically, the control references System.Web.Extensions Version 3.5 dll which is currently provided in the .NET 3.5 install; Reference for details : http://weblogs.asp.net/scottgu/archive/2007/07/30/asp-net-ajax-in-net-3-5-and-vs-2008.aspx

There is no special requirement for vs2k5 ; All editions of VS2k5 including express are able to run ASP.NET 2.0 applications and .NET 3.5 is simply an upgrade of extra extention dlls, nothing more. So make sure you have .NET 3.5 installed. One thing to note here is that you won't be able to use any new additions in .NET 3.5 that require compiler support such as linq,wcf, wpf etc, all things that jiffycms has no dependency on and you should be fine. Make sure you meet this requirement.

Simple howto- For Visual Studio 2005 development environment users :

You may try adding an assembly redirect in your current web.config file. You can do this in two ways, first, you can try by redirecting all bindings to System.Web.Extentions 3.5 (the latest version the editor is built on) to go to your current version in use (the older one).

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="3.5.0.0" newVersion="1.0.61025.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

note the oldversion and the new version? It basically takes any requests for 3.5 version and redirects to the older one that you are currently using.
This is supposedly the easiest way to get things rolling for you.

If the above doesn't work, here's a second method :

Another approach is to download and get the System.Web.Extentions 3.5 assembly. Then reference this assembly in your project manually. Finally add an assembly redirect to it in web.config like this :

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

Lastly, experiment with method 1 and 2 above, there is no perfect solution for VS2k5 users unfortunately.

Registering the custom httpHandler :

The toolkit requires that you add configuration settings to an httphandler in your web.config file. You can get the toolkit to register the handler automatically by dragging and dropping the control from the toolbox to the designer surface. A second option is to register the handler manually in web.config as follows :

add the following entry under the path Configuration/httpHandlers section for IIS6 :

<add verb="*" path="jiffycms.axd" type="Jiffycms.Net.Toolkit.WebResourceHandler" />

For IIS7, you need to make an entry under the path : Configuration/system.webServer/Handlers section as follows :

<add verb="*" path="jiffycms.axd" name="WebResourceHandler"
type="Jiffycms.Net.Toolkit.WebResourceHandler"
preCondition="integratedMode" />

for details, reference the following article :

http://www.jiffycms.net/Article/htmleditor-tutorials/23/Using-an-External-StyleSheet-with.aspx

If you need help, post on our forum http://www.jiffycms.net/forum/default.aspx

Quick start introduction tutorials
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/19/23/Using-an-External-StyleSheet-with.aspx
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/22/25/Setting-up-an-image-gallery-in.aspx

A quick preview of designtime features supported in VS.NET
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/16/21/Jiffycms-HTML-Editor-DesignView.aspx

Jiffycms HTML Editor V1.0 Quick links
Project homepage http://www.jiffycms.net/default.aspx
Tutorials http://www.jiffycms.net/article/htmleditor-tutorials.aspx (more coming, be patient)

Blog http://www.jiffycms.net/article/technical-blog.aspx

Post on the support forum below for questions you may have
Support forum http://www.jiffycms.net/forum/default.aspx

screen shots

Easily customize with custom themes you* yourself create easily

Now also supports RTL

More RTL

Inventors of the floating toolbar on an HTML Editor (maximum flexibility) :-)

Basic mode, perfect for blog comments

Commented Issue: Html Editor does not work with TabContainer [5096]

chadboettcher — Sat, 23 Jan 2010 00:45:31 GMT

I'm experiencing a similar issue with the ajaxToolkit:TabPanel. The designer are appears to be rendering out as a TextArea rather than an IFrame as it does when not in a tab control. I see the toolbars and icons but the design area is not visible.

I've also attached an image.

Updated Release: Jiffycms.Net.Toolkit V2.0.1.1 (gen 18, 2010)

jiffycms — Mon, 18 Jan 2010 22:22:55 GMT

Small bug fixes. No breaking changes. For any problems, please do report them on our forums.

1-Downlevel support was broken, fixed now!

2-Loading status wasn't centered within the media frame screen. This is fixed now! Online samples have been updated to reflect the change.

3- Bug in the color picker control where the clientside handlers for Ok and cancel buttons were fired twice. Fixed now

4- Bug in IE when changing the font fore color, it would instead apply background color. Fixed now

5- Bug in our ms word cleanup utility. The cleanup was replacing the color attribute with background-color css property. It should be color property instead. This is fixed now.

6- Bug in editor when using an underscore in the id eg: <cc1:Editor id="html_editor" ... /> note the underscore in the id, this was causing problems and truncating the request, Fixed now!

7- When clicking the save icon, last highlighted element in the document was being posted back to the server. This is fixed now.

8- Scroll position is now maintained in IE when a dialog window is launched by the editor

Released: Jiffycms.Net.Toolkit V2.0.1.1 (Jan 18, 2010)

Mon, 18 Jan 2010 22:22:55 GMT

Updated Release: Jiffycms.Net.Toolkit V2.0.1.1 (gen 18, 2010)

jiffycms — Mon, 18 Jan 2010 19:25:40 GMT

Released: Jiffycms.Net.Toolkit V2.0.1.1 (Jan 18, 2010)

Mon, 18 Jan 2010 19:25:40 GMT

Created Issue: Html Editor does not work with TabContainer [5096]

vhrc99 — Wed, 13 Jan 2010 16:19:26 GMT

Updated Wiki: Home

jiffycms — Mon, 11 Jan 2010 13:52:10 GMT

Project Description
Jiffycms is primarily a wysiwyg ASP.NET rich text HTML editor (RTE), but also contains an image picker control, image gallery, media frame (a sort of light box, much more advanced), a color picker and an update progress panel etc. All nicely contained within a single dll...

Online demo http://www.jiffycms.net/demo/default.aspx

For screenshots, scroll to the bottom of the page :-)

Update: 09/01/2010 jiffycms is now on twitter http://twitter.com/jiffycms. This is the fastest way to know all the latest fixes and what's going on. You are encouraged to subscribe to stay ontop of things.

Installation Requirements :

The control will work in Visual studio 2008 (our current development environment) and should work nicely under Visual studio 2005 ; The express editions of both 2k8 and 2k5 should work nicely too. Just make sure you have installed .NET 3.5 (specifically, the control references System.Web.Extensions Version 3.5 dll which is currently provided in the .NET 3.5 install; Reference for details : http://weblogs.asp.net/scottgu/archive/2007/07/30/asp-net-ajax-in-net-3-5-and-vs-2008.aspx

There is no special requirement for vs2k5 ; All editions of VS2k5 including express are able to run ASP.NET 2.0 applications and .NET 3.5 is simply an upgrade of extra extention dlls, nothing more. So make sure you have .NET 3.5 installed. One thing to note here is that you won't be able to use any new additions in .NET 3.5 that require compiler support such as linq,wcf, wpf etc, all things that jiffycms has no dependency on and you should be fine. Make sure you meet this requirement.

Simple howto- For Visual Studio 2005 development environment users :

You may try adding an assembly redirect in your current web.config file. You can do this in two ways, first, you can try by redirecting all bindings to System.Web.Extentions 3.5 (the latest version the editor is built on) to go to your current version in use (the older one).

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="3.5.0.0" newVersion="1.0.61025.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

note the oldversion and the new version? It basically takes any requests for 3.5 version and redirects to the older one that you are currently using.
This is supposedly the easiest way to get things rolling for you.

If the above doesn't work, here's a second method :

Another approach is to download and get the System.Web.Extentions 3.5 assembly. Then reference this assembly in your project manually. Finally add an assembly redirect to it in web.config like this :

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

Lastly, experiment with method 1 and 2 above, there is no perfect solution for VS2k5 users unfortunately.

Registering the custom httpHandler :

The toolkit requires that you add configuration settings to an httphandler in your web.config file. You can get the toolkit to register the handler automatically by dragging and dropping the control from the toolbox to the designer surface. A second option is to register the handler manually in web.config as follows :

add the following entry under the path Configuration/httpHandlers section for IIS6 :

<add verb="*" path="jiffycms.axd" type="Jiffycms.Net.Toolkit.WebResourceHandler" />

For IIS7, you need to make an entry under the path : Configuration/system.webServer/Handlers section as follows :

<add verb="*" path="jiffycms.axd" name="WebResourceHandler"
type="Jiffycms.Net.Toolkit.WebResourceHandler"
preCondition="integratedMode" />

for details, reference the following article :

http://www.jiffycms.net/Article/htmleditor-tutorials/23/Using-an-External-StyleSheet-with.aspx

If you need help, post on our forum http://www.jiffycms.net/forum/default.aspx

Quick start introduction tutorials
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/19/23/Using-an-External-StyleSheet-with.aspx
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/22/25/Setting-up-an-image-gallery-in.aspx

A quick preview of designtime features supported in VS.NET
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/16/21/Jiffycms-HTML-Editor-DesignView.aspx

Jiffycms HTML Editor V1.0 Quick links
Project homepage http://www.jiffycms.net/default.aspx
Tutorials http://www.jiffycms.net/article/htmleditor-tutorials.aspx (more coming, be patient)

Blog http://www.jiffycms.net/article/technical-blog.aspx

Post on the support forum below for questions you may have
Support forum http://www.jiffycms.net/forum/default.aspx

screen shots

Easily customize with custom themes you* yourself create easily

Now also supports RTL

More RTL

Inventors of the floating toolbar on an HTML Editor (maximum flexibility) :-)

Basic mode, perfect for blog comments

Updated Wiki: Home

jiffycms — Sat, 09 Jan 2010 17:18:45 GMT

Project Description
Jiffycms is primarily a wysiwyg ASP.NET rich text HTML editor (RTE), but also contains an image picker control, image gallery, media frame (a sort of light box, much more advanced), a color picker and an update progress panel etc. All nicely contained within a single dll...

Online demo http://www.jiffycms.net/demo/default.aspx

For screenshots, scroll to the bottom of the page :-)

Update: 09/01/2010 jiffycms is now on twitter http://twitter.com/jiffycms. This is the fastest way to know all the latest fixes and what's going on. You are encouraged to subscribe to stay ontop of things.

Installation Requirements :

The control will work in Visual studio 2008 (our current development environment) and should work nicely under Visual studio 2005 ; The express editions of both 2k8 and 2k5 should work nicely too. Just make sure you have installed .NET 3.5 (specifically, the control references System.Web.Extensions Version 3.5 dll which is currently provided in the .NET 3.5 install; Reference for details : http://weblogs.asp.net/scottgu/archive/2007/07/30/asp-net-ajax-in-net-3-5-and-vs-2008.aspx

There is no special requirement for vs2k5 ; All editions of VS2k5 including express are able to run ASP.NET 2.0 applications and .NET 3.5 is simply an upgrade of extra extention dlls, nothing more. So make sure you have .NET 3.5 installed. One thing to note here is that you won't be able to use any new additions in .NET 3.5 that require compiler support such as linq,wcf, wpf etc, all things that jiffycms has no dependency on and you should be fine. Make sure you meet this requirement.

Simple howto- For Visual Studio 2005 development environment users meeting these requirements :

You may try adding an assembly redirect in your current web.config file. You can do this in two ways, first, you can try by redirecting all bindings to System.Web.Extentions 3.5 (the latest version the editor is built on) to go to your current version in use (the older one).

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="3.5.0.0" newVersion="1.0.61025.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

note the oldversion and the new version? It basically takes any requests for 3.5 version and redirects to the older one that you are currently using.
This is supposedly the easiest way to get things rolling for you.

If the above doesn't work, here's a second method :

Another approach is to download and get the System.Web.Extentions 3.5 assembly. Then reference this assembly in your project manually. Finally add an assembly redirect to it in web.config like this :

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

Lastly, experiment with method 1 and 2 above, there is no perfect solution for VS2k5 users unfortunately.

Registering the custom httpHandler :

The toolkit requires that you add configuration settings to an httphandler in your web.config file. You can get the toolkit to register the handler automatically by dragging and dropping the control from the toolbox to the designer surface. A second option is to register the handler manually in web.config as follows :

add the following entry under the path Configuration/httpHandlers section for IIS6 :

<add verb="*" path="jiffycms.axd" type="Jiffycms.Net.Toolkit.WebResourceHandler" />

For IIS7, you need to make an entry under the path : Configuration/system.webServer/Handlers section as follows :

<add verb="*" path="jiffycms.axd" name="WebResourceHandler"
type="Jiffycms.Net.Toolkit.WebResourceHandler"
preCondition="integratedMode" />

for details, reference the following article :

http://www.jiffycms.net/Article/htmleditor-tutorials/23/Using-an-External-StyleSheet-with.aspx

If you need help, post on our forum http://www.jiffycms.net/forum/default.aspx

Quick start introduction tutorials
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/19/23/Using-an-External-StyleSheet-with.aspx
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/22/25/Setting-up-an-image-gallery-in.aspx

A quick preview of designtime features supported in VS.NET
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/16/21/Jiffycms-HTML-Editor-DesignView.aspx

Jiffycms HTML Editor V1.0 Quick links
Project homepage http://www.jiffycms.net/default.aspx
Tutorials http://www.jiffycms.net/article/htmleditor-tutorials.aspx (more coming, be patient)

Blog http://www.jiffycms.net/article/technical-blog.aspx

Post on the support forum below for questions you may have
Support forum http://www.jiffycms.net/forum/default.aspx

screen shots

Easily customize with custom themes you* yourself create easily

Now also supports RTL

More RTL

Inventors of the floating toolbar on an HTML Editor (maximum flexibility) :-)

Basic mode, perfect for blog comments

Updated Wiki: Home

jiffycms — Sat, 09 Jan 2010 13:24:35 GMT

Project Description
Jiffycms is primarily a wysiwyg ASP.NET rich text HTML editor (RTE), but also contains an image picker control, image gallery, media frame (a sort of light box, much more advanced), a color picker and an update progress panel etc. All nicely contained within a single dll...

Online demo http://www.jiffycms.net/demo/default.aspx

For screenshots, scroll to the bottom of the page :-)

Installation Requirements :

The control will work in Visual studio 2008 (our current development environment) and should work nicely under Visual studio 2005 ; The express editions of both 2k8 and 2k5 should work nicely too. Just make sure you have installed .NET 3.5 (specifically, the control references System.Web.Extensions Version 3.5 dll which is currently provided in the .NET 3.5 install; Reference for details : http://weblogs.asp.net/scottgu/archive/2007/07/30/asp-net-ajax-in-net-3-5-and-vs-2008.aspx

There is no special requirement for vs2k5 ; All editions of VS2k5 including express are able to run ASP.NET 2.0 applications and .NET 3.5 is simply an upgrade of extra extention dlls, nothing more. So make sure you have .NET 3.5 installed. One thing to note here is that you won't be able to use any new additions in .NET 3.5 that require compiler support such as linq,wcf, wpf etc, all things that jiffycms has no dependency on and you should be fine. Make sure you meet this requirement.

Simple howto- For Visual Studio 2005 development environment users meeting these requirements :

You may try adding an assembly redirect in your current web.config file. You can do this in two ways, first, you can try by redirecting all bindings to System.Web.Extentions 3.5 (the latest version the editor is built on) to go to your current version in use (the older one).

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="3.5.0.0" newVersion="1.0.61025.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

note the oldversion and the new version? It basically takes any requests for 3.5 version and redirects to the older one that you are currently using.
This is supposedly the easiest way to get things rolling for you.

If the above doesn't work, here's a second method :

Another approach is to download and get the System.Web.Extentions 3.5 assembly. Then reference this assembly in your project manually. Finally add an assembly redirect to it in web.config like this :

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

Lastly, experiment with method 1 and 2 above, there is no perfect solution for VS2k5 users unfortunately.

Registering the custom httpHandler :

The toolkit requires that you add configuration settings to an httphandler in your web.config file. You can get the toolkit to register the handler automatically by dragging and dropping the control from the toolbox to the designer surface. A second option is to register the handler manually in web.config as follows :

add the following entry under the path Configuration/httpHandlers section for IIS6 :

<add verb="*" path="jiffycms.axd" type="Jiffycms.Net.Toolkit.WebResourceHandler" />

For IIS7, you need to make an entry under the path : Configuration/system.webServer/Handlers section as follows :

<add verb="*" path="jiffycms.axd" name="WebResourceHandler"
type="Jiffycms.Net.Toolkit.WebResourceHandler"
preCondition="integratedMode" />

for details, reference the following article :

http://www.jiffycms.net/Article/htmleditor-tutorials/23/Using-an-External-StyleSheet-with.aspx

If you need help, post on our forum http://www.jiffycms.net/forum/default.aspx

Quick start introduction tutorials
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/19/23/Using-an-External-StyleSheet-with.aspx
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/22/25/Setting-up-an-image-gallery-in.aspx

A quick preview of designtime features supported in VS.NET
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/16/21/Jiffycms-HTML-Editor-DesignView.aspx

Jiffycms HTML Editor V1.0 Quick links
Project homepage http://www.jiffycms.net/default.aspx
Tutorials http://www.jiffycms.net/article/htmleditor-tutorials.aspx (more coming, be patient)

Blog http://www.jiffycms.net/article/technical-blog.aspx

Post on the support forum below for questions you may have
Support forum http://www.jiffycms.net/forum/default.aspx

screen shots

Easily customize with custom themes you* yourself create easily

Now also supports RTL

More RTL

Inventors of the floating toolbar on an HTML Editor (maximum flexibility) :-)

Basic mode, perfect for blog comments

Updated Wiki: Home

jiffycms — Sat, 09 Jan 2010 13:23:21 GMT

Project Description
Jiffycms is primarily a wysiwyg ASP.NET rich text HTML editor (RTE), but also contains an image picker control, image gallery, media frame (a sort of light box, much more advanced), a color picker and an update progress panel etc. All nicely contained within a single dll...

Online demo http://www.jiffycms.net/demo/default.aspx

For screenshots, scroll to the bottom of the page :-)

Installation Requirements :

The control will work in Visual studio 2008 (our current development environment) and should work nicely under Visual studio 2005 ; The express editions of both 2k8 and 2k5 should work nicely too. Just make sure you have installed .NET 3.5 (specifically, the control references System.Web.Extensions Version 3.5 dll which is currently provided in the .NET 3.5 install; Reference for details : http://weblogs.asp.net/scottgu/archive/2007/07/30/asp-net-ajax-in-net-3-5-and-vs-2008.aspx

There is no special requirement for vs2k5 ; All editions of VS2k5 including express are able to run ASP.NET 2.0 applications and .NET 3.5 is simply an upgrade of extra extention dlls, nothing more. So make sure you have .NET 3.5 installed. One thing to note here is that you won't be able to use any new additions in .NET 3.5 that require compiler support such as linq,wcf, wpf etc, all things that jiffycms has no dependency on and you should be fine. Make sure you meet this requirement.

Simple howto- For Visual Studio 2005 development environment users meeting these requirements :

You may try adding an assembly redirect in your current web.config file. You can do this in two ways, first, you can try by redirecting all bindings to System.Web.Extentions 3.5 (the latest version the editor is built on) to go to your current version in use (the older one).

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="3.5.0.0" newVersion="1.0.61025.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

note the oldversion and the new version? It basically takes any requests for 3.5 version and redirects to the older one that you are currently using.
This is supposedly the easiest way to get things rolling for you.

If the above doesn't work, here's a second method :

Another approach is to download and get the System.Web.Extentions 3.5 assembly. Then reference this assembly in your project manually. Finally add an assembly redirect to it in web.config like this :

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

Lastly, experiment with method 1 and 2 above, there is no perfect solution for VS2k5 users unfortunately.

Registering the custom httpHandler :

The toolkit requires that you add configuration settings to an httphandler in your web.config file. You can get the toolkit to register the handler automatically by dragging and dropping the control from the toolbox to the designer surface. A second option is to register the handler manually in web.config as follows :

add the following entry under the path Configuration/httpHandlers section for IIS6 :

<add verb="*" path="jiffycms.axd" type="Jiffycms.Net.Toolkit.WebResourceHandler" />

For IIS7, you need to make an entry under the path : Configuration/system.webServer/Handlers section as follows :

<add verb="*" path="jiffycms.axd" name="WebResourceHandler"
type="Jiffycms.Net.Toolkit.WebResourceHandler"
preCondition="integratedMode" />

for details, reference the following article :

http://www.jiffycms.net/Article/htmleditor-tutorials/23/Using-an-External-StyleSheet-with.aspx

If you need help, post on our forum http://www.jiffycms.net/forum/default.aspx

Quick start introduction tutorials
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/19/23/Using-an-External-StyleSheet-with.aspx
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/22/25/Setting-up-an-image-gallery-in.aspx

A quick preview of designtime features supported in VS.NET
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/16/21/Jiffycms-HTML-Editor-DesignView.aspx

Jiffycms HTML Editor V1.0 Quick links
Features http://www.jiffycms.net/default.aspx
Tutorials http://www.jiffycms.net/article/htmleditor-tutorials.aspx (more coming, be patient)

Blog http://www.jiffycms.net/article/technical-blog.aspx

Post on the support forum below for questions you may have
Support forum http://www.jiffycms.net/forum/default.aspx

screen shots

Easily customize with custom themes you* yourself create easily

Now also supports RTL

More RTL

Inventors of the floating toolbar on an HTML Editor (maximum flexibility) :-)

Basic mode, perfect for blog comments

Updated Wiki: Home

jiffycms — Sat, 09 Jan 2010 13:20:58 GMT

Project Description
Jiffycms is primarily a wysiwyg ASP.NET rich text HTML editor (RTE), but also contains an image picker control, image gallery, media frame (a sort of light box, much more advanced), a color picker and an update progress panel etc. All nicely contained within a single dll...

Online demo http://www.jiffycms.net/demo/default.aspx

For screenshots, scroll to the bottom of the page :-)

Installation Requirements :

The control will work in Visual studio 2008 (our current development environment) and should work nicely under Visual studio 2005 ; The express editions of both 2k8 and 2k5 should work nicely too. Just make sure you have installed .NET 3.5 (specifically, the control references System.Web.Extensions Version 3.5 dll which is currently provided in the .NET 3.5 install; Reference for details : http://weblogs.asp.net/scottgu/archive/2007/07/30/asp-net-ajax-in-net-3-5-and-vs-2008.aspx

There is no special requirement for vs2k5 ; All editions of VS2k5 including express are able to run ASP.NET 2.0 applications and .NET 3.5 is simply an upgrade of extra extention dlls, nothing more. So make sure you have .NET 3.5 installed. One thing to note here is that you won't be able to use any new additions in .NET 3.5 that require compiler support such as linq,wcf, wpf etc, all things that jiffycms has no dependency on and you should be fine. Make sure you meet this requirement.

Simple howto- For Visual Studio 2005 development environment users meeting these requirements :

You may try adding an assembly redirect in your current web.config file. You can do this in two ways, first, you can try by redirecting all bindings to System.Web.Extentions 3.5 (the latest version the editor is built on) to go to your current version in use (the older one).

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="3.5.0.0" newVersion="1.0.61025.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

note the oldversion and the new version? It basically takes any requests for 3.5 version and redirects to the older one that you are currently using.
This is supposedly the easiest way to get things rolling for you.

If the above doesn't work, here's a second method :

Another approach is to download and get the System.Web.Extentions 3.5 assembly. Then reference this assembly in your project manually. Finally add an assembly redirect to it in web.config like this :

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

Lastly, experiment with method 1 and 2 above, there is no perfect solution for VS2k5 users unfortunately.

Registering the custom httpHandler :

The toolkit requires that you add configuration settings to an httphandler in your web.config file. You can get the toolkit to register the handler automatically by dragging and dropping the control from the toolbox to the designer surface. A second option is to register the handler manually in web.config as follows :

add the following entry under the path Configuration/httpHandlers section for IIS6 :

<add verb="*" path="jiffycms.axd" type="Jiffycms.Net.Toolkit.WebResourceHandler" />

For IIS7, you need to make an entry under the path : Configuration/system.webServer/Handlers section as follows :

<add verb="*" path="jiffycms.axd" name="WebResourceHandler"
type="Jiffycms.Net.Toolkit.WebResourceHandler"
preCondition="integratedMode" />

for details, reference the following article :

http://www.jiffycms.net/Article/htmleditor-tutorials/23/Using-an-External-StyleSheet-with.aspx

If you need help, post on our forum http://www.jiffycms.net/forum/default.aspx

Quick start introduction tutorials
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/19/23/Using-an-External-StyleSheet-with.aspx
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/22/25/Setting-up-an-image-gallery-in.aspx

A quick preview of designtime features supported in VS.NET
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/16/21/Jiffycms-HTML-Editor-DesignView.aspx

Jiffycms HTML Editor V1.0 Quick links
Features http://www.jiffycms.net/default.aspx
Tutorials http://www.jiffycms.net/article/htmleditor-tutorials.aspx (more coming, be patient)

News http://www.jiffycms.net/article/news.aspx
Blog http://www.jiffycms.net/article/technical-blog.aspx

Post on the support forum below for questions you may have
Support forum http://www.jiffycms.net/forum/default.aspx

screen shots

Easily customize with custom themes you* yourself create easily

Now also supports RTL

More RTL

Inventors of the floating toolbar on an HTML Editor (maximum flexibility) :-)

Basic mode, perfect for blog comments

Updated Wiki: Home

jiffycms — Fri, 08 Jan 2010 16:21:56 GMT

Project Description
Jiffycms is primarily a wysiwyg ASP.NET rich text HTML editor (RTE), but also contains an image picker control, image gallery, media frame (a sort of light box, much more advanced), a color picker and an update progress panel etc. All nicely contained within a single dll...

Online demo http://www.jiffycms.net/demo/default.aspx

For screenshots, scroll to the bottom of the page :-)

Installation Requirements :

The control will work in Visual studio 2008 (our current development environment) and should work nicely under Visual studio 2005 ; The express editions of both 2k8 and 2k5 should work nicely too. Just make sure you have installed .NET 3.5 (specifically, the control references System.Web.Extensions Version 3.5 dll which is currently provided in the .NET 3.5 install; Reference for details : http://weblogs.asp.net/scottgu/archive/2007/07/30/asp-net-ajax-in-net-3-5-and-vs-2008.aspx

There is no special requirement for vs2k5 ; All editions of VS2k5 including express are able to run ASP.NET 2.0 applications and .NET 3.5 is simply an upgrade of extra extention dlls, nothing more. So make sure you have .NET 3.5 installed. One thing to note here is that you won't be able to use any new additions in .NET 3.5 that require compiler support such as linq,wcf, wpf etc but for the rest, you should be fine. Make sure you meet these requirements.

Simple howto- For Visual Studio 2005 development environment users meeting these requirements :

You may try adding an assembly redirect in your current web.config file. You can do this in two ways, first, you can try by redirecting all bindings to System.Web.Extentions 3.5 (the latest version the editor is built on) to go to your current version in use (the older one).

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="3.5.0.0" newVersion="1.0.61025.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

note the oldversion and the new version? It basically takes any requests for 3.5 version and redirects to the older one that you are currently using.
This is supposedly the easiest way to get things rolling for you.

If the above doesn't work, here's a second method :

Another approach is to download and get the System.Web.Extentions 3.5 assembly. Then reference this assembly in your project manually. Finally add an assembly redirect to it in web.config like this :

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/>
<bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>

Finally, experiment with method 1 and 2 above, there is no perfect solution for VS2k5 users unfortunately.

Registering the custom httpHandler :

The toolkit requires that you add configuration settings to an httphandler in your web.config file. You can get the toolkit to register the handler automatically by dragging and dropping the control from the toolbox to the designer surface. A second option is to register the handler manually in web.config as follows :

add the following entry under the path Configuration/httpHandlers section for IIS6 :

<add verb="*" path="jiffycms.axd" type="Jiffycms.Net.Toolkit.WebResourceHandler" />

For IIS7, you need to make an entry under the path : Configuration/system.webServer/Handlers section as follows :

<add verb="*" path="jiffycms.axd" name="WebResourceHandler"
type="Jiffycms.Net.Toolkit.WebResourceHandler"
preCondition="integratedMode" />

for details, reference the following article :

http://www.jiffycms.net/Article/htmleditor-tutorials/23/Using-an-External-StyleSheet-with.aspx

If you need help, post on our forum http://www.jiffycms.net/forum/default.aspx

Quick start introduction tutorials
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/19/23/Using-an-External-StyleSheet-with.aspx
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/22/25/Setting-up-an-image-gallery-in.aspx

A quick preview of designtime features supported in VS.NET
http://www.jiffycms.net/Article/HtmlEditor-Tutorials/2009/3/16/21/Jiffycms-HTML-Editor-DesignView.aspx

Jiffycms HTML Editor V1.0 Quick links
Features http://www.jiffycms.net/default.aspx
Tutorials http://www.jiffycms.net/article/htmleditor-tutorials.aspx (more coming, be patient)

News http://www.jiffycms.net/article/news.aspx
Blog http://www.jiffycms.net/article/technical-blog.aspx

Post on the support forum below for questions you may have
Support forum http://www.jiffycms.net/forum/default.aspx

screen shots

Easily customize with custom themes you* yourself create easily

Now also supports RTL

More RTL

Inventors of the floating toolbar on an HTML Editor (maximum flexibility) :-)

Basic mode, perfect for blog comments