Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
Windows Phone

Windows Phone 8 : Designing for the Phone - Designing with Visual Studio

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
5/14/2013 6:05:49 PM

Although Blend provides the strongest tooling for design including the features we’ve seen like animations and visual state manager support, at times switching to Blend is unnecessary for smaller layout and property changes. Starting in Visual Studio 2012, the XAML designer is powered by Blend’s design surface.

If you start with a new project, your XAML is shown in a split view, as shown in Figure 1.

Figure 1. Showing just the Design View

Image

In this split view, you can simply double-click the designer Icon (where the arrow is pointing) to show only the design view (which I find easier). After you have the design view opened, you can see the Properties pane is similar to the Blend pane (in that it’s collapsible and uses the same editors as Blend), as shown in Figure 2.

Figure 2. The Blend-like Property Pane in Visual Studio

Image

The missing piece here for most of the Blend-like design is the Objects and Timeline pane. In Visual Studio this is called the Document Outline. As Visual Studio can’t do animations. You can click the dedicated Document Outline button to show this pane (see Figure 3).

Figure 3. Showing the Document Outline

Image

When you have this view, you can simply work with the design surface exactly like you would in Blend. The underlying code for this design surface is the same one used in Blend. For example, you can simply right-click the ApplicationBar section of the Document Outline to add an ApplicationBar to your design, as shown in Figure 4.

Figure 4. Adding an ApplicationBar in Visual Studio

Image

So for those simple XAML changes, Visual Studio can be a faster way to modify your design.

Other -----------------
- Windows Phone 7 : 3D Game Development (part 4) - Rendering 3D Models
- Windows Phone 7 : 3D Game Development (part 3) - The Game Class
- Windows Phone 7 : 3D Game Development (part 2) - Rendering 3D Primitives
- Windows Phone 7 : 3D Game Development (part 1) - 3D Game Concepts
- Windows Phone 8 : Phone-Specific Design (part 3) - Using the Pivot Control in Blend
- Windows Phone 8 : Phone-Specific Design (part 2) - Using the Panorama Control in Blend
- Windows Phone 8 : Phone-Specific Design (part 1) - The ApplicationBar in Blend
- Windows Phone 7 : AlienShooter Enhancements (part 2) - Tombstone Support, Particle System
- Windows Phone 7 : AlienShooter Enhancements (part 1) - Load and Save Game State
- Windows Phone 7 Programming Model : Application Execution Model
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
 
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server