C# for Java/*nix programmers.

Question

I am mainly a java programmer, using linux/os x for as long as i remember. I am extremely comfortable in emacs and usually prefer doing things through command line.

I need to create a internet explorer addon for our next project. I need to intercept url ie is about to download and if they meet certain criteria pass it to our application.

So my questions are,

• How can i build a c# project through command line so i can integrate it with our current build process.
• Current i have windows 2k installed in a virtual machine that i use for testing. Is there going to be any compatibility problems.
• I am assuming i am going to be creating a dll and inject it to ie to intercept url's. Am i on the right track?

Answer 1

Here are responses to your questions:

• Use the C# Command Line Compiler. MSDN has an entire section devoted to its use.
• Not for an IE add-on. If you plan to do more, using some newer libraries, you may run into problems unless you're running Windows XP or later. For IE addons, 2000 should be fine.
• That's the basic idea. I'd refer to the MSDN articles on creating add-ons for IE, such as this one showing how to make custom menus.

Be aware, though, that you'll have a more difficult time if you avoid using Visual Studio (or some other IDE). There is no reason not to use VS, especially since you can use the Express Edition for free. If you're doing that, you can use msbuild instead of csc directly, and it will simplify your build process (even if you build from the command line).

However, the productivity gains from a good IDE will come in handy, especially for C#.

Answer 2

Responses to your questions:

• If you use Ant maybe this will help. If you use Maven, maybe this will help. Otherwise, I'd just use MSBuild or NAnt.
• Can't say for sure. I would guess that the IE API would be the same on each of the platforms. YMMV.
• I'm busy writing an IE addon at work and I'm using SpicIE. It's very straightforward and simplifies the IE API drastically.

I've read in the comments elsewhere that you're not a fan of VS. I would probably use it (or MonoDevelop/SharpDevelop if they can create .csproj) to create the .csproj that can be used as an input to MSBuild. It might save you time rather than having to learn the syntax of the file.

Answer 3

If you give up the IDE, you give up one of the best debuggers on the planet and the best code-completion I've ever seen. Other than the fact that it will be a new system to you, there is no reason to claim that you can develop faster in EMACS. Everything you need is in the IDE, and there are keyboard shortcuts to mostly everything.

If you computer can handle the work load, I really see no good reason not to use Visual Studio.

edit: the newest version of visual studio won't run on anything less than XP sp2, to my recollection. This is most likely because the new versions of .NET won't run on anything lower than that... which would be a huge compatibility problem.