Re: Working With WPF in D2007/D2008?

I.P. Nichols wrote:
"Robert Giesecke" wrote:
I.P. Nichols wrote:

Blend uses the Visual Studio *.proj file as the interface so that if either Visual Studio or Blend make changes to either a XAML or it's code behind file, the other one knows that a change has happened and can reload the changed files.

That *is* the MSBuild file.

Maybe I'm being too persnickety but in the vernacular of both MSBuild and Visual Studio they are referred to as "Project" files. For instance if you have a C# Visual Studio project named foo, you can build the project with the command line "MSBuild foo.sln". If you rename or delete the foo.csproj file and try to build with that same command line, MSBuild will complain with the error message "MSBUILD : error MSB1009: Project file does not exist."


MSBuild has a special handler for solution files. But you can always call msbuild on the project files directly.
From MSBuild's POV all of them are the same. It will populate "properties" with every node in the project file that it doesn't know of, so that all build targets can access those values. (like click-once, or the compiler)

The main difference between a C# project and an Oxygene or Delphi one is, that C# has this line:
<Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" />
While Oxygene has this one;
<Import Project="$(MSBuildExtensionsPath)\RemObjects Software\Chrome\RemObjects.Chrome.targets" />

And this line is totally uninteresting for Blend.
Blend only cares about the files and folders that are listed in the project file.

So as I said, you should be able to open Delphi.Net projects with Blend (in theory), but I don't think that you would really want to do that.
Because D.Net cannot handle every code that the WPF codegen can emit.
(And I do keep repeating myself here *g*)
.

Relevant Pages

  • Re: Working With WPF in D2007/D2008?
    ... C# projects, Oxygene projects, etc. ... The difference between those is only additional nodes that Blend won't care about. ... Visual Studio or Blend make changes to either a XAML or it's code behind file, the other one knows that a change has happened and can reload the changed files. ... As to what the RO guys needed to do to get Blend to know what to do with Oxygene/Chrome code behind *.pas files is best answered by them but this might not be the most appropriate place for such a response. ...
    (borland.public.delphi.non-technical)
  • Re: Dotfuscator and ClickOnce
    ... Visual Studio uses MSBuild to build and publish ClickOnce ... Fortunately, there's a AfterCompile target, which is built after the ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Thinking Clearly
    ... I agree and thank Brian, I wasn't aware of that excellent link. ... Actually it's msbuild that's the key that unlocks everything. ... Visual Studio installed - msbuild comes as part of the WinFX SDK. ... of benefit to, and easily consumable by, Highlander developers. ...
    (borland.public.delphi.non-technical)
  • Re: Working With WPF in D2007/D2008?
    ... Maybe I'm being too persnickety but in the vernacular of both MSBuild and Visual Studio they are referred to as "Project" files. ... If you rename or delete the foo.csproj file and try to build with that same command line, MSBuild will complain with the error message "MSBUILD: error MSB1009: Project file does not exist." ...
    (borland.public.delphi.non-technical)
  • Re: Dotfuscator and ClickOnce
    ... This does not work with the Dotfuscator Community Edition shipped with Visual Studio 2005. ... Visual Studio uses MSBuild to build and publish ClickOnce ... Fortunately, there's a AfterCompile target, which is built after the ... building and publishing within VS and what's important is that you can see ...
    (microsoft.public.dotnet.languages.vb)