internet explorer - Advantages & Disadvantages of writing IE addons in .NET -
since .net developer, planning write ie addon in .net. here have experience with/in developing ie extensions in .net can share knowledge?
specifically know advantages & disadvantages of using .net task in comparison atl com.
i'd rather advantages & disadvantages not bound ie addons more programming languages , platforms.
.net:
- it easier , more safe c++
- easy create , program ui
- requires end user machines have specific .net framework installed (you can run addon on compatible frameworks)
- uses more memory
- requires declare winapi functions , constants if need them
c++ (atl com approach):
- uses less memory
- can statically linked not require .net frameworks, visual c++ runtimes, etc (in other words run everywhere)
- easy call winapi
- requires more knowledge , more tough .net
- awful ui editor (at least built-in atl/mfc)
so if .net guy pay attention compatibility different .net framework versions. other stuff minor.
Comments
Post a Comment