casey.s.marshall at gmail.com
Tue Aug 12 16:10:30 EDT 2008
Bryan Murphy wrote:
> Hey guys,
> I've got a problem where the trunk build of monodevelop keeps changing
> the TargetFrameworkVersion from v3.5 to v2.0 in my csproj files. The
> problem with this is that I can no longer compile under Visual Studio
> 2008 since we make extensive use of v3.5 features. VS does not make
> those features available when you are targeting the v2.0 framework, and
> hence our builds break.
> Right now, I have to manually change the framework version every time I
> commit a change to a csproj file, but it's easy to forget. Is there a
> way I can force monodevelop to leave this alone?
The only way I could think of to handle this was to introduce a 3.5
version, and I'm patching MD locally to do that.
I'll attach the patch I'm applying, which seems to mostly work. There
are some issues with code completion, though, when initially loading
projects, so it's clearly not everything that's required.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4051 bytes
Desc: not available
Url : http://lists.ximian.com/pipermail/monodevelop-list/attachments/20080812/065214d9/attachment.bin
More information about the Monodevelop-list