New to plugin-development - what language/IDE to use?

[mila06]

I would like to start some nPVR-plugin development. Can I select which .NET language I would like to use? I'd rather use C#, as i have done some small projects in that(VS 2008) .NET 3.5.

What language do you use for nPVR plugin-development?

[sub]

NPVR was written with C#. There was a few sample c# plugins posted in another thread.

[whurlston]

You can use either VB.Net or C#. C# is probably the prefered language of most plugin developers (mine for sure). Sub provided some C# samples but I would have to look for them as I'm not exactly sure where they are at the moment.

Edit: Dang it, late again.

[mila06]

Ok, thanks guys!

I found some sample plugins - C# it is and of we go then!

Which .NET version is used - 3.0 or 3.5?

[sub]

I still target .NET 2.0 so users dont have to download a huge runtime. (ie 20MB vs 160MB in later .NET runtims)

[mvallevand]

As a plugin developer I would have preferred that with NextPVR you did take the logical jump. Most new users seem to be Win7 users anyway, who don't need to do this download, and I'm confident that the existing XP users who haven't already d/led .NET 3.5 for other apps that require it would have been willing to make this small investment of time.

Martin

[sub]

There was more to the decision than the size.

[InVermont]

As a plugin developer I would have preferred that with NextPVR you did take the logical jump. Martin

Is there any reason a plugin shouldn't target .Net 3.5? I've been toying with development (Visual C# Express 2010), and have no problems with the dll targeting 3.5
I had issues with .NET 4, where it couldn't find the correct version of dll's, GetImage tossed odd exceptions, ect.

[mvallevand]

Ok sorry my misunderstanding I thought that size mattered. My limited understanding was that because 2.0 and 3.5 share the same runtime (CLR) there were no upward compatibility concerns.

Martin

[sub]

Is there any reason a plugin shouldn't target .Net 3.5? I've been toying with development (Visual C# Express 2010), and have no problems with the dll targeting 3.5

.NET 2.0, .NET 3.0 and .NET 3.5, all use the 2.0 CLR, so it should be compatible. The difference between these versions of .NET is really in the extra baggage that is bundled in like the WinFX framework in 3.0, and LINQ etc added in 3.5.