HTML WYSIWYG editor for c# desktop application

I need to create an html wysiwyg editor in my windows form application with drag-drop features. If i use web-browser component to display the html page , user wont be able to interact with the controls in the page. Any suggestions ,how to go about???

Thanks in advance....
Sree
LVL 4
msreekmAsked:
Who is Participating?
 
purpleblobCommented:
With regards your previous to last comment, sorry I wasn't aware this utility was a 2003 build.

Anyway in answer to your last points.

Simply go to the references section of your solution, it will probably highlight mshtml and AxShDocView as missing, delete them then right mouse click and select Add Reference...

Now in the COM tab locate Microsoft HTML Object library - this will give the mshtml reference and press select, now locate (from the same tab) Microsoft Internet Controls and select, then press OK. This should supply the interops you require.
0
 
AJMartinCommented:
Consider over-riding the drag-drop events? That way the user will still be able to click links on the page.

I hope that helps!
0
 
purpleblobCommented:
I believe the web browser control which comes as part of IE can be switched to editor mode, this may get you a long way along in your goal.

Check out http://www.itwriting.com/htmleditor/index.php this may be of interest
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
msreekmAuthor Commented:
thanks ill get back to u soon ....
0
 
msreekmAuthor Commented:
            Microsoft.Mshtml.dll Primary Interop Assembly looks too large for this application... (7820 kb) ,really not sure if this will work...  because this application is supposed to be downloadable for users thru internet.

 
0
 
purpleblobCommented:
There are ways of working with the controls without using the interop assembly - you could hand code the interfaces that you intend to use, but not sure how much work this would require - I wonder if you could uses a tool such as Lutz Roeder's Reflector to decompile the interop and copy and paste the interfaces you require.

Otherwise you'll going to have to write an HTML editor by hand, obviously with the browser control you'll have something which outputs as per IE.
0
 
msreekmAuthor Commented:
the HTMLEDIT project doesnt open in vs.net earlier version, I guess it was done in vs.net 2003, which i donot have , how to proceed???
0
 
msreekmAuthor Commented:
the HTMLEDITOR contorl project doesnt open in vs.net earlier version, I guess it was done in vs.net 2003, which i donot have , how to proceed???
0
 
purpleblobCommented:
Check out http://www.eggheadcafe.com/articles/20030425.asp there's a util here (if I recall) which can convert 2003 to 2002 projects
0
 
msreekmAuthor Commented:
that itself was made in 2003 , how will i use tht?
error message-
c:\win.......framwork\v1.1.4322  mwscorwks.dll not found???
0
 
msreekmAuthor Commented:
I tried creating new solution and project in  the earlier studio version  and then added all files to it . created a win form and user contrl project and added resp files.. now iam not able tofigure out what references are made in usercontrol and win form project. i get lot of errors while compiling like.

C:\rediffHtmlEdit\HtmlEditorControl\HtmlEditorControl.cs(18): The type or namespace name 'mshtml' could not be found (are you missing a using directive or an assembly reference?)

C:\rediffHtmlEdit\HtmlEditorControl\HtmlEditorControl.cs(1746): The type or namespace name 'AxSHDocVw' could not be found (are you missing a using directive or an assembly reference?)


how do i find out what references should i make?
0
 
msreekmAuthor Commented:
Sorry I didnt specify that iam not using the control you said...I got it from ...
http://windowsforms.net/articles/htmleditor.aspx
0
 
msreekmAuthor Commented:
thnks i fixed it with a conversion tool i obtained from the belwo link
which apparently microsoft support team gave me.

here is the mail to share with you guys ...

------------------------------------------------------------------

the issue you are having is the contents of the forms/controls associated resx files. If one open the Html Editor Control resx file you will see the following entry:
 
editorWebBrowser.BackgroundImage
System.Resources.ResXNullRef, System.Windows.Forms, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
 
For VS2002 the version should be: 1.0.3300.
There is a program someone wrote at http://www.codeproject.com/macro/vsconvert.asp?print=true which does the conversion.
 
The steps listed are
In SLN files, the 8.0 must be replaced with 7.0.
In vcproj files (and only vcproj), the 7.10 part must be replaced by 7.0.
In VB.NET or C# project files, 7.10.xxxx is replaced with 7.0.9466, where xxxx is the build number of VS.NET 7.1
Also in VB.NET and C# projects, the schema version 2.0 should be replaced with 1.0.
In RESX files, the types declared are 1.0.5000 and must be replaced with 1.0.3300.
Finally, in RESX files (binary streams), the base-64 encoded part that describes the version of the stream must change from LjAuNTAw to LjAuMzMw (basically base-64-encoded versions of 1.0.5000 and 1.0.3300 respectively)
 
Hopefully this helps.

Carl Nolan
Senior Consultant
US National Services


------------------------------------------------------------------


now eerything is working fine after conversion.

I want to deploy this application in a web server , to be downloaded for the users from a web page. now the entire application compiles to around 1mb with all dlls. How do i package this with the runtime so that all users who doesnt have clr installed should be able to install it and run from their desktops. (something like IMs (MSN,YAHOO) . setup should automatically detect the runtime presence. now will the inclusion of runtime  increase the size of application considerably?

thanks for all answers. I will release the points after this ...
0
 
KevinSean206Commented:
There is a workspace on GotDotNet.com that deals with this issue by modifying the boot-strapper for the packaged vs.net installer to automatically detect and download (if neccessary) the .Net framework as opposed to the default behavior of the installer which directs the user to the proper URL to download the framework themselves. To find it, look through the workspace directory on gotdotnet.com

Kevin.
0
 
KevinSean206Commented:
There is a workspace on GotDotNet.com that deals with this issue by modifying the boot-strapper for the packaged vs.net installer to automatically detect and download (if neccessary) the .Net framework as opposed to the default behavior of the installer which directs the user to the proper URL to download the framework themselves. To find it, look through the workspace directory on gotdotnet.com

Kevin.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.