guitar chords pdf free downloadmicrosoft visual basic 6 0 free download for windows xplord of the rings the battle for middle earth ii downloadkaspersky internet security 2014 download for windows xp sp2
Below is often a snapshot with the Web page the way it appeared on 1/23/2016. This will be the version with the page which was used for ranking pursuit results. The page might have changed because it was last cached. To see what probably have changed minus the highlights, proceed to the current page.
We have highlighted matching words that include the page below.The team blog in the Expression Blend and Design products.
We released important news today concerning the Expression group of products. Please visit the Expression Community site for details.
If you've watched the BUILD keynotes and sessions, you could have seen some exciting aspects of Expression Blends support for Metro-style applications.
For all future news and updates concerning Expression Blend, please go to our new team blog called BlendInsider. The BlendInsider blog can provide the types of content you found hereand hopefully additional!
This blog will likely be kept around for archival purposes, but no new content will likely be added.
As imaginable, right after a major release like there was, most people shift our focus slightly towards speaking about and sharing utilizing some on the cool latest features we released. In this initially a two-part series, I hope to create up with the long period of inactivity about this blog by sharing two Windows Phone focused videos that Unni, Billy, and I recorded for Channel 9.
The first video with this list is a that walks you through, with a breakneck speed, most on the new features we combined with Expression Blend to make building Windows Phone 7 apps easier:
Through the guise of creating a Bing Search application, I cover features starting from our Device Panel to Application Bar support to earning Sample Data coming from a Class file. You can learn more about these traits by taking a look at some of my more in-depth Windows Phone 7-focused articles.
The templates they created cover an array of common UIs that you'll see, so you can use these directly is likely to projects or simply just as a method to obtain inspiration. Before you can go of that, naturally, download the templates from codeplex first.
As always, if you could have any questions, go ahead and comment below. If you recorded some interesting videos, post them inside the comments likewise.
Today, we've released one more version with the Windows Phone Developer Tools. You can download it below:First, download solutions below:
This installer will automatically install free, phone-flavored versions of Expression Blend, Visual Studio 2010, and XNA Game Studio.
If you have now Expression Blend 4 installed, unlike earlier releases, running this installer will get more existing version of Expression Blend 4 and provide you the chance to create Silverlight, WPF, and Windows Phone applications:
Thanks to everyone who's got provided feedback within the last few number of releases that can help us are able to this stage. As always, if you've any additional feedback, you can post them around the Windows Phone Developer Forums.
Its been quite some time since we released an update for all of us working on Windows Phone 7 projects! Well, wait get rid of! Today weve released an new version of Expression Blend that supports all with the latest changes meant to the Windows Phone 7 runtime in addition to some cool latest features.
First, download solutions below:
As you will notice, you no longer require to download and install Expression Blend separately. You can just run the only Windows Phone Developer Tools installer and acquire Windows Phone variants of Expression Blend, XNA Game Studio, and Visual Studio free of charge.
This version of Expression Blend installs and runs side-by-side with Expression Blend 4 and just supports working together with Windows Phone projects.
As mentioned earlier, beyond supporting the changes designed to the runtime since last release, weve added plenty of new functionality that produces designing Windows Phone 7 applications easier. Some on the more notable features are described below.
Because your applications will be displayed in different orientations, themes, and accent colors, weve made it easier for that you visualize within Expression Blend what you would resemble.
The Device Panel now will provide you with easy access to preview between Landscape and Portrait orientations, Light and Dark themes, and Accent color.
For example, here is often a preview of what the application looks like inside the default Dark theme:
This allows one to design and make certain that your applications look how you want irrespective of which light/dark mode an individual has their phone in.
Windows Phone 7 applications emphasize consistent usage of text like a key design element. To make it easier for someone to preview and apply existing text styles, weve added a chance to preview inline just what a particular text style would seem like:
In this release, we now have exposed a really early preview of the support for allowing that you design the Application Bar. You have the opportunity to create an Application Bar, add Application Bar Buttons, and add Application Bar Menu Items. Because Application Bar Buttons display a 48x48 PNG icon, you'll be able to specify your individual icon or pick at a collection of icons we've got provided in your case:
A future writing will review in greater detail the way you use what you might have today to design an operating Application Bar!
Because Windows Phone applications are certainly page centric, we decided for making navigating between pages easy. To navigate in one page to an alternative, we exposed a Navigate To context menu:
This menu is usually accessed once you right click any element which you wish to start the navigation when clicked.
We have revised the FluidMoveBehavior to become on par with all the improvements we created for Silverlight 4 4. You can learn more as to what this means by reading Kenny Youngs blog post within this topic.
Unlike Silverlight and WPF certainly where an full keyboard for input is virtually always guaranteed, Windows Phone users may possibly not have that luxury when working away at their phones. While a on-screen keyboard is obtainable, because of the size with the screen, finding the full keyboard with all from the keys appear on-screen might not be ideal for every situation either. It may be useful to users should the keys displayed were optimized with the type of information they will be entering during this particular moment.
To address that want, we improved our support for your InputScope property on TextBox that allows one to specify which kind of data is going to be entered:
For example, if Number was selected for your InputScope on the TextBox, can do for you the on-screen keyboard seems like when you consentrate on it within the emulator/device:
Notice you are not seeing the regular full keyboard. Instead, you happen to be seeing a keyboard optimized just for numerical input.
As always, if you've any questions or feedback, please twenty-four hours a day comment below or post on our forums.
A weeks ago, some Expression Blend staff presented in the TechEd conference stuck New Orleans this coming year!
You can flick through all with the sessions to the information.
Creating healthy looking and functioning applications is actually difficult. It requires developing a good eye for design, just about all requires some technical exposure to how to generate the design functional.
As you'll be able to probably guess, it can be our goal to help you you use Expression Blend, Visual Studio, and our related tools to produce those great applications. We spend a substantial amount of time adding additional features and making existing features better to help you you function that. Making improvements on the applications is only 1 side of how we try to help you you create great applications, however.
The medial side involves assisting you to better discover how to actually create great applications, and that we try healthy to provide some valuable training resources. Some notable shoutouts include plus the Expression Community sites. While considering videos or reading tutorials is effective, we desired to go further and as well provide you with a library of xamlcode samples that showcase something small, something specific, something cool. We felt that, on many occasions, simply being capable to deconstruct how something was done might be equally or even more useful in finding out how to do something.
This library of xamlcode snippets, known better by its relatives and buddies as the Pattern Library, lives just as one extension on the Expression Gallery:
You can learn more in regards to the Pattern Library by reading Lars Powers newsletter article introducing it.
Please you can download and spend playtime with the patterns. If there is something you are feeling is missing, please feel to allow us know or simply create it yourself and upload it.
Today at Internet Week in NYC, we announced the available appointments of Expression Studio 4. You can download the trial of Expression Studio 4 Ultimate that has Expression Blend 4 and SketchFlow by clicking below:
Keep watching this web site for more news, updates, and in-depth discusses some in the new features that weve introduced. Until then, here are a few related links:
Note that if you happen to be currently doing Windows Phone development, please not upgrade to the last version of Expression Blend 4 yet. We will release an new version of all of our own phone components within the future, so please carry on using Expression Blend 4 RC.
Of course, no major release will be possible minus the feedback all of you could have provided, so thanks!
While the PathListBox control offers an easy way to lie down items along a path, setting up a carousel control that appears 3 dimensional and has now smooth scrolling requires additional functionality that people did not have time for you to do in Expression Blend 4. Ive come up with PathListBoxUtils sample situated on CodePlex to produce the tools that make developing a carousel much like the one shown below quite simple:
Visit the Carousel tutorial to view how to build this example, and you may view all PathListBoxUtils-related tutorials here.
Its been some time since the last article where I promised to publish about all from the behaviors that ship with Expression Blend in greater detail. Ill try to get more prompt from the future. Today, lets look in the ControlStoryboardAction plus the StoryboardCompletedTrigger.
Storyboards are one on the primary ways you create animations in Silverlight, WPF, and Windows Phone using Expression Blend. Creating a storyboard is pretty easy, truly using a storyboard including having it play just isn't. To help using this type of, you could have the ControlStoryboardAction.
Simply put, the ControlStoryboardAction is surely an Action that allows you to definitely select a storyboard and specify everything you would like to accomplish to it:
Lets check out some in the properties it includes in greater detail.
When you are looking for this behavior, you can find only two properties you need to stress about. They are the ControlStoryboardOption and Storyboard properties.
From here you are able to choose whether you would like to play a storyboard, stop it, toggle between play/pause, pause, resume, or jump to your end.
The only missing piece to date is knowing which storyboard to affect. Not to worry, simply because you specify the storyboard while using the aptly named Storyboard property:
This property are listed all with the Storyboards your behavior has access to. Once you've got selected a Storyboard, that you are done!
This trigger invokes an Action every time a specified storyboard set through Storyboard property has fully be completion. Of course, because it is really a trigger, you are able to use it with any Action.
In Expression Blend 4, one with the new samples we added is referred to as MockupDemonstration. If you havent stood a chance to put it to use yet, you'll be able to open MockupDemonstration through the Welcome screen, which can be available after you first start Expression Blend or once you click Help and click Welcome Screen. In the Welcome screen, click Samples, after which click MockupDemonstration:
As you are able to tell quickly from exploring this sample, this sample boasts a handful of controls designed to assist you create prototypes easily. The catch is these controls only exist inside this particular sample. Since some of you could have requested that it will be useful to own these controls available outside on the sample, this short article will explain how for making these mockup controls easily obtainable in other projects.
To enable mockup controls for almost any SketchFlow project, copy the mockup controls run-time and design-time assemblies in the MockupDemonstration sample to your pre-configured Libraries folder through using the steps below:
1. Copy both and Design folder from:
for WPF projects, follow this task but copy files from Libraries Debug
2. Add copied files towards the following destination:
Computer OS C: Program Filesx86 Microsoft Expression Blend 4 Libraries Silverlight 4.0
for WPF paste the copied files on the NETFramework folder from the previous factor to Libraries 4.0
3. Restart Blend. You can now begin using mockup controls by clicking the Mockups category from the Assets panel the correct assembly reference is automatically combined with your project.
If you've any questions or comments, please you can post below or on our forums.
At MIX, we released a young preview in our support for building applications for Windows Phone 7 that only ran with a pre-release version of Framework.
If you might have been suppressing on upgrading for the latest versions of Expression Blend, Visual Studio, 4, wait no longer! Today, we in addition to the Windows Phone team are releasing an update on the components we released recently to work on one more version Framework 4.
Besides the RC posted above, you will require the following components installed for developing Windows Phone apps:
Besides support 4, there are some general improvements to your overall design experience, emulator updates, and breaking API changes. You can get a broader overview around the Windows Phone Developer blog.
As always, we like to hear from you. Please go ahead and comment below or use our forums here.
As nearly all of you know, a couple weeks ago we released the discharge candidate version of Expression Blend 4. Shortly after lots of you experienced a chance to spend playtime with it, a few of you reported that Expression Blend crashes during launch.
If you happen to be one of those people whose Expression Blend crashes after launch, please download this minor revision in the release candidate we released a couple weeks ago:
If you arent having any problems launching Blend, there is no need to upgrade. There are no additional features or changes besides some changes to create sure Expression Blend runs properly on launch.
We were competent to detect this problem thanks largely from the error reports those of you on this crash submitted. We constantly undergo all with the crash reports we receive, and that we try to fix as the majority of them as is possible.
While produce your own . you never ought to experience crashes from running Expression Blend, if you undertake experience an accident, please submit the mistake reports!
Recently, a final versions of both Silverlight 4 4 happen to be released! To coincide with this particular, were releasing a release candidate version of Expression Blend 4 that you may use to a target them:
There are two things you really want to know about this release.
First, if you're doing Windows Phone development, it's not necassary to use the Expression Blend 4 RC. We will offer an update to suit your needs soon with updated components, but inside the meantime, please use Expression Blend 4 Beta.
Second, this turmoil Expression Blend 4 targets one more versions of Silverlight 4 4, you'll be able to share your creations with all the rest with the world. You no longer are tied to only sharing your creations in source code form and for private testing.
If you havent experienced a chance to browse the sessions from MIX10 that showcased Expression Blend 4, all the backlinks below should assist you out:
Authoring for Windows Phone, Silverlight 4 and WPF 4 with Expression Blend
This post only focuses for the sessions from MIX which are Expression Blend specific. By now, all with the sessions from MIX really should be available online, so head over for the MIX Sessions page to look at more: /Sessions
Click here to observe Kennys MIX 2010 session that covers a lot in the topics which you see in this article.
In Expression Blend, weve been thinking for any loooong time about how to produce it ever easier to build great animated visual effects quickly on top on the Silverlight and WPF runtimes. Weve been taking a look at large-scale animation needs since Blend 2 SP1 and steadily building features to cope with those needs, therefore we think weve reached critical mass. With Blend 4, we've a compelling group of technologies that actually work very well together.
This blog post is often a companion towards the Dynamic Layout and Transitions demo app that weve placed from the Expression Gallery at /en-us/DynamicLayoutTrans. That app reveals the features whose motivations are described here.
Since its inception, Blend has offered keyframed editing of Silverlight and WPF properties via Storyboards. While I wont enter specific particularly that here, it forms the cornerstone for all the characteristics described below. Some of these characteristics work right from Storyboards you create among others create Storyboards behind the scenes for your benefit and sometimes both.
Lets start with turning the time back 24 months. In Expression Blend 2 SP1, we introduced the States Panel, which edits VisualStates and VisualStateGroups for Silverlight 2 and WPF 3.5 while using WPF Toolkit. This introduced the notion of any state like a means of communication between visuals and code, making it dramatically better to describe a number of visual changes. Based on input, the control code could decide ought to enter what state, and also the visuals would decide what changes were within that state plus the time it latched onto transition between any set of two states you may choose most state changes to consider 0.25s, but want Pressed state changes for being instantaneous.
This proved to be an exceptionally effective tool, nonetheless it had limitations. The core VisualStateManager runtime which well call VSM in the future could only do linear interpolations in the values being set. This works well for opacity and transform offsets, but doesnt are very effective for discrete properties or data that isnt known until runtime. Also, not every animation scenarios are determined by state changes. So we put our thinking caps on about how exactly we could acquire more scenarios to operate in a way that designers could rapidly tool the end results.
In V3, we added four primary enhancements in this region. The first was EasingFunctions, which can be critical to making property animations contain the right feel. Weve got each of the classics quadratics, cubics, bounce, elastic, etc. Plus, you are able to write your individual EasingFunction in C or VB and rub it to any animation you'd like. This is all supported in Silverlight 3 and WPF 4. EasingFunctions might be applied in an individual animation or keyframe, and you are able to apply a default EasingFunction for a entire state transition.
The second would be a GoToStateBehavior in addition to Blends Behaviors engine, which made it very easy to program your state change logic directly within the markup without code. Like all of Blends Behaviors, it is possible to simply drag it from my Asset Panel onto any elements you end up picking.
Those two enhancements just made the previous scenarios run better. We also wanted to handle new classes of scenario. The first one we tackled was the problem of elements opting a StackPanel or WrapPanel. Traditionally, these factors have snapped into place just as one application changes elements or changes size, and now we wanted an even transition that users could control. So we introduced the FluidMoveBehavior to generate it feasible for an element to see the layout manager whenever it transferred to a new spot, and lessen its progress with the animation controlled by one particular EasingFunctions we described earlier. So now its all to easy to have your elements animate into place in a speed you select!
Heres a picture from the feature doing his thing. Theres no longer room about the first line with the purple rectangle, so its moving for the beginning with the second row as well as the other elements are moving to generate space. Technically, coming from a layout perspective, the weather in motion are in reality at their destinations already but by adding the suitable transforms on the top, we result in the change look smooth through the visual perspective that users love.
The fourth enhancement we made was one of the most challenging for many people. We realized that many times, customers wanted different states inside their control to obtain different layouts entirely, however respond to active layout changes from the application. For example, one layout may have a number of task panes visible outside of the working area, and another may have one or more these panes hidden. Customers needed to describe these different layouts with states to acquire a good separation between their visuals as well as their business logic, even so the properties that required to change between these states werent properties that may be smoothly interpolated. For example, how would you interpolate between and?
What we learned was that in the event like these, users werent satisfied using the direct property animations our system as long as they just wanted it to seem right, and rendering it look right required that any of us animate a morph in the change as opposed to the change itself. So we wrote an electric train engine that would go on a layout snapshot prior to state change, take another layout snapshot following your state change, and create an easy morph between your start and end positions, employing the duration and EasingFunction with the users choosing. We dubbed this FluidLayout, and you'll be able to turn it on here:
Just click that little button, and your complete layout adjustments to that VisualStateGroup is going to be animated between states regardless of whether it seems impossible. Well even simulate a Visibility change by using an opacity simulation. Note that youll convey more success when you click this before you begin making layout changes otherwise, once you move a thing, itll create translate/scale animations which don't respect layout, because thats the most effective that the typical VSM are capable of doing.
Its hard to try and do justice to the present feature in images, but heres my best attempt. In this situation, the Timeline Pane is inside process of shrinking towards the leftmost column, which I configured by changing the Panes property in a very state. Similarly, I changed the RowSpan with the pink rectangle, and it is within the process of skyrocketing taller to be a result.
In Blend 4, weve managed for taking these themes further, and also have three more toys for designers to use. Lets start with animating things in and out of lists. In V3, you may apply a FluidMoveBehavior for your ListBox, plus the other items would dutifully make room for ones new item or up close the space. But there wasnt any easy way to effectively control the item that had been itself being added or removed; in the event you were clever, you can rig up some events for making an element animate on entry, so you had to become really really clever and pollute your computer data model in unfortunate ways to create an element animate on exit. We worked closely while using Silverlight team to manufacture a solution here that you are able to tool effectively, and it is called LayoutStates. To find them, first edit the ItemContainerStyle:
And then, note these three new VisualStates inside States Panel:
You can make use of these states to model what an element seems as if just before its loaded, what it seems as if after its been loaded, and what it appears to be just before its unloaded. Silverlight will likely then animate the state of hawaii changes for you in the appropriate times, as the items are combined with or removed through the list. Remember to give a FluidMoveBehavior to your ItemsPanel template note its presence inside Edit Additional Templates submenu, a few pictures above, and place AppliesTo Children, to get the other components to move out in the way. Note that when your ItemsPanel is usually a VirtualizingStackPanel, your ListBox needs to have set to Standard, or else you should learn one with the other new tricks below.
Heres among this for doing things the middle item is only entering a list.
The next feature we added is another inside vein of simulation. In V3, we added FluidLayout to VSM in order to get an easy and realistic morph between two states, nevertheless it got us to thinking regarding the other sorts of morphs we might perform. Enter TransitionEffects. Whereas transition effects in video editing offer a pixel-based transition derived from one of video clip to a new, Blends TransitionEffects give a pixel-based transition in one state completely to another. In Blend, a TransitionEffect is usually a PixelShader that's an animatable Progress property. We are shipping several of the in our SDK, and if you already know HLSL you are able to write your personal. Heres how we set one up:
As configured here, all state changes within the LayoutStates group will do a Smooth Swirl Grid pixel-based TransitionEffect, taking one second is actually a cubic ease. You can certainly set an alternative transition for virtually any individual state change if desired. Some on the TransitionEffects have properties to help expand customize them; for instance, Smooth Swirl Grid permits you to control how much subdivision as well as the intensity with the twisting effect, but those properties are under the combo dropdown within the picture. Heres a screenshot of their TransitionEffect doing his thing:
The final feature we added can be something that weve been attempting to wrap our minds around for several years. Weve realized that in plenty of applications, visuals will move in one part from the application to a new even though the visuals in many cases are generated from data. In a true MVVM design the place that the data model should be aware nothing around the visuals, its extremely tough to get such effects.
What weve done is train the visuals to learn more around the data model specifically, to learn FluidMoveBehavior to associate positions with data as opposed to with visuals. This uses a little bit of explanation, but is remarkably all to easy to use you may create an animated list-detail example completely from scratch in about two minutes.
What you want is to the large chair inside details view show up to grow out on the small chair inside master list. All we have now to do is locate the Image element inside ItemTemplate to the ListBox, and offer it a FluidMoveTagSetBehavior that can register it using the FluidMove system. That seems like this:
Note how the Tag property points too element will probably be tagged based on its DataContext, which can be the model item behind the visuals. Next, theres a FluidMoveBehavior within the detail Image, which seems as if this:
The other half in the connection is made while using InitialTag field that is certainly set to DataContext. This means that if your detail element appears, it'll consider the registered position of that DataContext to get the place it can appear to are derived from. And thats everything! Heres a screenshot of the app doing his thing; observe that in this case I set the FluidMoveBehavior for the entire Grid, so the details would animate as well as the image.
Theres a lot happening behind the scenes, but weve were able to boil this complex scenario about bat roosting two simple properties. This system could even be used to animate objects in one list to an alternative list.
If I had included all of our own future investigations in this subject, this article would be doubly long because it is already. Were working hard to deal with more and more scenarios within the simplest ways possible. Rest assured that material hearing about much more improvements someday inside the not too distant future!
If you might have any opinions or feedback, please you can comment below.
Architect, Expression Blend
As many of you understand, today was the very first day of MIX - Microsofts annual conference for designers and developers. Just like previous years, there has been lots of great news coming out in the conference.
The two big things we announced are Expression Blend 4 Beta along with an add-in to Expression Blend that provides you a chance to build applications for that Windows Phone.
Christian Schormann includes a nice introduction to Expression Blend 4 and the extra features in it, so if you need to learn more, go read his article.
Of course, there are going to be plenty of posts within the upcoming days and weeks that dive into detail on which weve released and announced today, so a lot more.
Over the following couple of weeks, it appears to be like best if you go over some in the behaviors we shipped to be a part of Expression Blend 3. Many of you've mentioned you would like to learn more around the stock behaviors we ship and the way they are used, this blog will probably be a good interim solution with the until we properly add your feedback into our future product documentation.
First standing on our list is a of one of the best behaviors that any of us shipped, the GoToStateAction!
As you realize, you've the power to define and modify your individual visual states inside your applications:
Having a visual state is simply one part of the needs to become done. The other part is definitely being capable to switch for the visual state for the appropriate time. For predefined visual states that you just find within your controls, the mechanism for switching states is made in. For visual states that you simply create on your individual, you will have to supply the logic for switching the visual states yourself.
That is when this behavior is available in. The GoToStateAction allows one to easily switch visual states given the right event using just your Properties Inspector. The following screenshot will show you the standard behaviors UI customized using the properties exposed by GoToStateAction:
Lets look at many of these properties in greater detail.
Like I mentioned earlier, this behavior primary functionality is in allowing one to change the visual state. How it does could wish for some further inspection, so lets look on the various properties in depth.
The visual state is set with the StateName property. By default, you will see every one of the states defined within your root scope ie: UserControl or Window no matter where you drag/drop this behavior onto. You can change this by targeting this behavior at another element.
For example, the default target is my UserControl where I have two states defined:
If I were to another element, such like a Button made up of its own states, the StateName list is populated with those states instead:
I spoke a whole lot about changing the target that a states are derived from, so lets look in the TargetName property the place that the element you desire to target is in fact specified.
If you would like to target states living somewhere else like another Control or UserControl, it is possible to use the TargetName property to affect the element you wish to point to. As mentioned earlier, the default value for TargetName could be the root scope for instance your UserControl or Window.
If you happen to be trying to pick out something that isnt easily selectable visually, you'll be able to hit the miscroscopic button to determine a flat listing of most of your elements. That is similar to what we see inside Objects and Timeline panel.
You can switch states suddenly, or you'll be able to smoothly transition into states. The UseTransitions property is what controls what your behavior will work. By default, the UseTransitions property is checked, but you may uncheck it when you want a sudden switchover for your new state.
Hopefully this helped offer you a summary in the GoToStateAction and ways in which it is usually used. If you might have any questions, please go ahead and comment below.
For a restricted time, there is usually a 30% discount on all Microsoft Expression 3 products Microsoft Expression Studio Expression Web, both full and upgrade versions with the Microsoft Online Store for US-based customers:
No promo code required in any respect just navigate to the store and add on the shopping cart!
Ok, pop-quiz time. Below, you can find two screenshots I took from two different applications:
Can you tell what on earth is different between the two images? If you said the button inside the second image seems a number of pixels off from your image within the top or something similar, that you are wrong. The UI depicted in both on the screenshots is likely same. Yes, it became a trick question.
While both applications look almost exactly the same when run, lets consider both of the applications when opened in Blend. Here is what the applying depicted in Screenshot 1 appears to be:
As it is possible to tell, there is usually a major discrepancy involving the first and second screenshot when viewed in Blend. More specifically, the other version with the application seems to get missing some UI and also the button is just not styled in any way.
The source on the discrepancies have to complete with what Blend actually shows for the design surface. By and large, Blend is often a XAML editor. Anything defined in XAML, we are going to do good to display it on our design surface. For visuals defined within your code-behind files, you possibly will not always be capable to see them in Blend.
This is in which the differences between two apps is caused by. In the first app, everything was defined in XAML. In the next app, some from the visuals were defined in XAML, but a many with the visuals weren't. That is why Blend is just showing an incomplete subset of what the job actually seems like when you view it within the design surface. This is usually a problem.
The word problem might be a harsh word due to this, even so the outcome is under ideal should your application is usually a collaborative effort between someone technical and someone less technical. If that you are a developer, being in a position to visualize code to make changes could be straightforward. If that you are more design oriented, investigating code to define the looks and feel connected with an application isn't natural. You would prefer something that appears like the application depicted in Screenshot 1 where things are exposed in Blends design surface and it is possible to make changes visually without writing code.
The first and obvious answer that I have is to get you stay away to add controls, define layout, or perform other visual tasks using code. The reason is always that, because you saw inside the screenshot with the second application, Blends design surface wont be able that can help you out.
Of course, you will find many instances when such an extreme solution will never work. It is common for several applications to fall under a gray area where visuals are partly defined in XAML and partly defined in code. Fortunately, you will discover some simple steps you may take to generate designers more productive while still giving developers the pliability to develop the application form.
If you've got visual content that needs for being added programmatically, make certain that content is looked as UserControls. The reason is that it is possible to define the UserControl to make changes entirely within Blend. Programmatically, you'll be able to add this UserControl which could have been edited inside Blend to you without sacrificing the designability on the UserControl itself.
Create Styles in XAML, Apply them Programmatically
Sometimes, UserControls might be a bit excessive. For example, inside the second screenshot, I have a button which is unstyled:
Instead of creating a dedicated UserControl to wrap your styled button, you could potentially just define the form in Blend and programmatically apply the design. Lets say you could have a style called GreenButtonStyle defined inside your Resources panel:
To apply this style in your button, use this code: