Are there limitations to using SpicIE (with C#) to develop an IE extension? If an IE extension is developed in SpicIE, and then later needs to be developed as a BHO (C++?), will it have to be rebuilt from scratch?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Are there limitations to using SpicIE (with C#) to develop an IE extension? If an IE extension is developed in SpicIE, and then later needs to be developed as a BHO (C++?), will it have to be rebuilt from scratch?
I don’t think you will be limited if you use this, as it’s mostly a thin layer between IE and the extension that uses it. Even if something’s missing, the CLR has powerful interop mechanisms, and last, you have SpicIE source.
If you ever need to port it over to a C++ project, yes, you will have to rewrite it, but the logic should be very similar, as the interfaces you will use are mostly IE’s COM interfaces (IHtmlxxx and all that jazz: http://msdn.microsoft.com/en-us/library/aa741322(v=VS.85).aspx). This is the same whether you’re working in C# or C++.
PS: since the source is provided, I would definitely try to merge SpicIE code with my own code, and build the whole in a single assembly, as this would ease deployment.