Re: xFx Plugins - C# 2005 Express

["drodegeb" <drodegeb@xxxxxxxxx>]

I have been playing around with the NewEmailOSD plugin, also with
VS2005 Express.  I saw the same problem, but I was able to get around
it by downloading the Source for the xapframework and xapframework gui
runtime, then re-compiling them in order (ex. xapframework, copy dll
files to gui refrences, compiled gui, copied resources to plugin,
compiled.  Only had to deal with a few changes in the schema for the
email, and compiles get a few warnings about obsolete methods which
should be cleaned up but don't hurt anything right now.

I was able to get the plugin working though.

Dave

--- In xAP_developer@xxxxxxx, "g8kmh" <g8kmh@m...> wrote:
>
> I figured that .NET 2.0 was likely to be the problem but the clean
> build and the fact it didn't barf at runtime fooled me.
>
> Hopefully a .NET 2.0 version will also 'encourage' plugin authors to
> bring their code up to the latest framework version as well which
> then would truly allow single runtimes and multiple plugins. One
> difficulty at the moment for non-developers is identifying which plug-
> in works with which xFx framework assembly/runtime.
>
> Lehane
>
>
> --- In xAP_developer@xxxxxxx, Stuart Booth <lists@x> wrote:
> >
> > On Fri, 11 Nov 2005 12:49:07 -0000, "Edward Pearson"
> > <edward.mailgroup@b...> wrote:
> >
> > >The probkem here is probably that VS05 uses .Net Framework
2.0
> rather that
> > >1.1.
> >
> > That's a good point actually, a 2.0 DLL is being found by a v1.1
> > application. It might not be getting loaded as a result. I
haven't
> > tried this out myself yet (see below).
> >
> > > I'm not sure how they interoperate, or if it's possible to
get
> VS05 to
> > >target .Net1.1 (even though it needs 2.0 to run itself since
> that's what
> > >it's written in). Stuart - any ideas? It's be great if this
worked
> as VS05
> > >is rather nice!
> >
> > Indeed!
> >
> > The plan is to release a final .NET v1.1 xFx SDK package and
leave
> > that as a legacy release alongside an upgraded .NET v2.0 xFx SDK
> > package which will be much more complete than before (examples,
an
> > actual [small] application or two, tech notes, HOWTOs etc, FAQs
etc)
> >
> > I've still got to remove VS2005 beta2 and upgrade to the final
> release
> > of VS2005.NET and then I can finally convert ALL my xFx projects
to
> > .NET 2.0. So far I've been running a parallel VS2005 solution
with
> > only a handful of key components converted so that I wasn't
losing
> > .NET v1.1 compatibility.
> >
> > That's a project for the w/e I think.
> >
> > S
> > --
> > Stuart Booth <stuart@x>
> > xAPFramework.net - a xAP software development framework for .net
> >
> > http://www.xapautomation.org/     
 http://www.xapframework.net/
> >
>