Hi All -
I had a problem that I thought I share with you the solution.
I integrated the FCKEditor and the .NET source code into a project of mine. I tried to use the:
to set the session path to my dynamic file storage. The problem I tracked down was that the SessionID was changing (yes, within the same application/project) between my page in which the Session was set and the:
where the file connector was stored. As it turns out, apparently by design, .NET will revert to ASP (not .NET) cookie handling if an HTM/HTML page is served from the server, which the IFRAME that stores the FCKEditor is (you can view more detail on this at:
I'm not sure of any more elegant workarounds, so I'm going to rename all FCKEditor items to be .aspx rather than .html so the session state in maintained throughout.
While there may be a way to have all htm pages parsed through the .NET isapi rather than the ASP api, in my environment I need both.
Hopefully this can help out fellow .NETters who may be having trouble maintaining session state through their implementation.
Workaround: .NET creates new sessions
Hi All -