[MonoDevelop] Visual Studio 2005 Import

[Lluis Sanchez]

El jue, 21-09-2006 a las 12:24 +0100, Gideon de Swardt escribió:
> Is everybody for native support for VS.NET? 
> 
> I think native support would provide needed functionality and high
> flexibility for users to switch between VS.NET, SD and MD. Especially as
> VS.NET developers would not switch over immediately, it is process and
> native support would allow them to test drive MD without having to convert
> their projects. I know this was a feature that I requested, back in the days
> when I was test-driving SD.
> 
> > Notice that after the project is loaded, it will look like to any other
> > native MD project, and it will be built and executed using the MD build
> > system.
> 
> So to implement native support for VS.NET project does not depend on XBuild?

It's your choice. It doesn't need to.

> 
> > > A questions that just jump straight out at me, would be how would
> > > current AddIns integrate with VS.NET 2005 project and solution files?
> > 
> > Add-ins interact with projects using the MonoDevelop.Projects object
> > model, so the format used to read the project is not relevant.
> > 
> > > I know that for instance the WebReference AddIn would have to change to
> > > use the native WebReference xml element for VS.NET projects instead of
> > > just adding ProjectFiles to MD project and hiding it them from the user.
> > > In fact the AddIn would require a separate NodeBuilder for loading
> > > WebReferences for VS.NET 2005 projects.
> >
> > The IFileFormat implementation should take care of it. At load time, it
> > could parse the WebReference xml element and add a ProjectFile to the
> > project being read, and do the reverse operation when saving.
> 
> Wouldn't it make sense to add dedicated WebReference elements to the MD
> project file format, the same as the current Reference elements. This way
> you don't have to convert one way for reading and then back again for saving
> for VS.NET projects, but all projects will handle them the same?

Web reference support is implemented in an add-in (which btw is not yet
part of MD). If that add-in is based on the xml format used by VS,
that's ok to me.

Lluis.