is there a #region ... #endregion equivalent for xaml files?

Question

as the subject says... some of my xaml files are getting quite big so would be great to collapse parts like we can with code with #region .. #endregion...

thanks

Dan

Answer 1

AFAIK no

Answer 2

I was just having a conversation with another WPF dev about exactly this.  We both agree that it would be a GREAT feature because XAML (well, XML) is not highly readable.  Hey Microsoft....looking for a new feature to bring joy to the hearts of your WPF developer community?

 

Answer 3

Just adding my voice - I too would love regions in XAML code!


(You're on a roll today Josh!)

Answer 4

 

pitching in as well: that would be great.

 

as an aside: when I open a xaml file, the first thing I do is collapse everything with cntrl-M-L
But, that's certainly not as usefull as regions ;-)

Answer 5

Whatever kind of facility they provided would have to be compatible with XML and there are already XML editors out there that will collapse/expand XML sections.  Oxygen or Stylus will both do it.  If there were XML "section" elements it would muddy up the 1-1 correspondence between elements and objects.  Personally I think it would gum things up more than clarify them.

Answer 6

ditto darrellp. 

 

Additionally, wysiwyg tools like blend and cider would not know what to do with the regions when you drag elements around on the design surface (just like they currently don't know what to do with xml comments).  They would have to make assumptions that may or may not be accurate about xml elements outside of their subtree.  This is never a good idea in xml.

 

Maybe it could be done with some sort of xml-based metadata tags, but I'm not convinced its a value add.

Answer 7

 I add my voice too.

---

love

Answer 8

This would be a very nice feature.

Hey Doc,

The fact that an automated tool would not know what to do with it does not mean that the feature is any less valuable.  Besides, if you are editing your XAML with a GUI tool, regions would not be needed anyway!

Answer 9

Also please add command and shortcut for collapsing all regions in XML. Something like Ctrl+M,O that we have in C# editor now.

Answer 10

its been 6 months... anything yet?  i would Love to see this feature as well.

Answer 11

I would love this feature aswell :)

Answer 12

Yet another vote for this... Raw XAML sucks, too verbose.

Or maybe collapsing a XAML element could be more selective about what info is shown.  Right now you collapse it and the name of element remains.  If more stuff remained it would be far more useful.

So maybe not adding a new XAML element, but a specially-formatted comment pair?

Answer 13

Please let me vote for this too.
It should not be so hard to include this with the .net4 improvements

I don't need something more fancy than this example :

<!--#region test1-->

 

 

     <WrapPanel Visibility="{Binding PrnDiagsVisibility}" Margin="3">
     ...
     </WrapPanel>

 

 

<!--#endregion-->

 

 

 

 

Answer 14

Please let me vote for this too.
It should not be so hard to include this with the .net4 improvements

I don't need something more fancy than this example :

<!--#region test1-->

     < WrapPanel Visibility ="{ Binding PrnDiagsVisibility }" Margin ="3">
     ...
     </ WrapPanel >

<!--#endregion-->

I couldn't agree more with this. When collapsed, the XML comments can disappear and be shown as they are in the typical code editor: a white rectangle with a gray border with the label inside (pretty much the string of text between '#region ' and '-->'. When expanded, it can be just as shown above for easy editing... just like it is in the regular code editor.

This solution is perfect because it's specific enough to be easily parsed and detected and thus implemented easily (the collapsing/expanding framework is obviously already there) AND it doesn't break the XML format or introduce any proprietary tags that would break readability or the reading/editing-ability in other editors.

You, sir. I like your style.

Answer 15

Hi,

This  definitely is a value add

Hoping to see such a feature soon :)

 

Thank You

---

Please mark posts as answers/helpful if it answers your query. This would be helpful for others facing the same kind of problem

Answer 16

I guess this is not exactly the right forum to vote, but still... Yes, please add this.

Answer 17

Regions in XAML would be a great feature.

Answer 18

Yes, we want it! Is there a place we can vote it up as a proposed feature or something?

Answer 19

Is there a place we can vote it up as a proposed feature or something?

Microsoft Connect?

This would be a nice feature! I was thinking of the same this past weekend.

Answer 20

XML regions could be implemented as a special container-control that incapsulates other elements, but has no visual character itself, and is skipped during interpretation just like XML comments. In your wysiwyg editor, it may appear as a subtle box into which you can drag elements. In XAML code, the elements are thus children of the region, while at run-time the elements appear as though they were stand-alone.

This allows your wysiwyg editor to visually reflect the region.

Answer 21

Just posted this XAML Regions Extension I whipped up:

http://visualstudiogallery.msdn.microsoft.com/3c534623-bb05-417f-afc0-c9e26bf0e177

Answer 22

Thanks a lot !

Answer 23

Jacob, I LOVE your extension,

It got me up & working *immediately*, with absolutely no fuss, when I was *struggling* to turn on a similar feature in VSCommands.

---

Yann

(plus ça change, plus c'est la même chose!)

Answer 24

Amazing thank you!

Answer 25

I was looking for something like this, thank u!