metastock professional 8 0 downloadmaxis widget workshop downloadmalwarebytes anti malware pro free download full versionhitman 3 free download softonic
Below is usually a snapshot on the Web page because it appeared on 1/23/2016. This may be the version in the page that had been used for ranking your quest results. The page could possibly have changed because it was last cached. To see what may have changed devoid of the highlights, navigate to the current page.
We have highlighted matching words that come in the page below.The team blog in the Expression Blend and Design products.
We released important news today concerning the Expression class of products. Please visit the Expression Community site for details.
If you might have watched the BUILD keynotes and sessions, you can have seen some exciting reasons for having 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 a lot more!
This blog are going to be kept around for archival purposes, but no new content are going to be added.
As you can think of, soon after a major release like there was, most people shift our focus slightly towards dealing with and sharing utilizing some in the cool additional features we released. In this to begin a two-part series, I hope for making up for that long period of inactivity with 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 but one that walks you through, with a breakneck speed, most in the new features we combined with Expression Blend which will make building Windows Phone 7 apps easier:
Through the guise of making a Bing Search application, I cover features including our Device Panel to Application Bar support to Sample Data from the Class file. You can learn more about these traits by investigating some of my more in-depth Windows Phone 7-focused articles.
The templates they created cover numerous common UIs you will see, so you can use these directly is likely to projects or simply just as a way to obtain inspiration. Before you can inflict of that, certainly, download the templates from codeplex first.
As always, if you've any questions, go ahead and comment below. If you recorded some interesting videos, post them inside the comments at the same time.
Today, we now have released a final version in 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 currently have Expression Blend 4 installed, unlike earlier releases, running this installer will remodel your existing version of Expression Blend 4 and provide you with the power to create Silverlight, WPF, and Windows Phone applications:
Thanks to everyone who's provided feedback during the last number of releases to help you us reach this stage. As always, if you might have any additional feedback, do post them about the Windows Phone Developer Forums.
Its been some time since we released an update for anyone working on Windows Phone 7 projects! Well, wait no longer! Today weve released an new version of Expression Blend that supports all on the latest changes created to the Windows Phone 7 runtime together with some cool the 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 Windows Phone Developer Tools installer and find Windows Phone variants of Expression Blend, XNA Game Studio, and Visual Studio without cost.
This version of Expression Blend installs and runs side-by-side with Expression Blend 4 in support of supports working together with Windows Phone projects.
As mentioned earlier, beyond supporting the changes designed to the runtime ever since the last release, weve added many new functionality that produces designing Windows Phone 7 applications easier. Some from 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 you to definitely visualize within Expression Blend what you would appear to be.
The Device Panel now will give you easy access to preview between Landscape and Portrait orientations, Light and Dark themes, and Accent color.
For example, here can be a preview of what the application looks like within the default Dark theme:
This allows someone to design and be sure that your applications look and the choice of want in spite of which light/dark mode anyone has their phone in.
Windows Phone 7 applications emphasize consistent by using text as being a key design element. To make it easier for that you preview and apply existing text styles, weve added the opportunity to preview inline exactly what a particular text style would seem like:
In this release, we now have exposed an exceptionally early preview in our support for allowing someone to design the Application Bar. You have a chance 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 may specify your own personal icon or pick from your collection of icons we now have provided to suit your needs:
A future post will review in greater detail the way you use what you've got today to design an operating Application Bar!
Because Windows Phone applications are incredibly page centric, we decided to create navigating between pages easy. To navigate derived from one of page to an alternative, we exposed a Navigate To context menu:
This menu could be accessed whenever you right click any element that you just wish to start the navigation when clicked.
We have revised the FluidMoveBehavior to get on par with all the improvements we created for Silverlight 4 4. You can learn more by what this means by reading Kenny Youngs blog post within this topic.
Unlike Silverlight and WPF in which a full keyboard for input is virtually always guaranteed, Windows Phone users mightn't have that luxury when working away at their phones. While a on-screen keyboard is accessible, considering the size with the screen, obtaining the full keyboard with all on the keys appear on-screen is probably not ideal for many situations either. It may be necessary to users if your keys displayed were optimized with the type of information they can be entering during that particular moment.
To address which need, we improved our support for that InputScope property on TextBox that allows you to definitely specify what type of data will likely be entered:
For example, if Number was selected to the InputScope with a TextBox, is going to do the on-screen keyboard appears to be when you give attention to it within the emulator/device:
Notice you are not seeing the standard full keyboard. Instead, you happen to be seeing a keyboard optimized limited to numerical input.
As always, if you could have any questions or feedback, please twenty-four hours a day comment below or post on our forums.
A couple of weeks ago, several Expression Blend downline presented with the TechEd conference located in New Orleans in 2010!
You can search all on the sessions to the information.
Creating nice looking and functioning applications is actually difficult. It requires which has a good eye for design, it requires some technical know-how about how to create the design functional.
As you are able to probably guess, it truly is our goal that can help you use Expression Blend, Visual Studio, and our related tools to generate those great applications. We spend a lot of time adding additional features and making existing features better to assist you accomplish that. Making improvements for the applications is only 1 side of how we try to aid you create great applications, however.
The other part involves aiding you better discover how to actually create great applications, and that we try good to provide some valuable training resources. Some notable shoutouts include plus the Expression Community sites. While thinking about videos or reading tutorials is advantageous, we desired to go further plus provide you with a library of xamlcode samples that showcase something small, something specific, something cool. We felt that, on many occasions, simply being in a position to deconstruct how something was done could be equally or more useful in learning to do something.
This library of xamlcode snippets, known better by its family and friends as the Pattern Library, lives just as one extension towards the Expression Gallery:
You can learn more regarding the Pattern Library by reading Lars Powers newsletter article introducing it.
Please you can download and enjoy the patterns. If there is something you sense is missing, please feel permit us know or maybe create it yourself and upload it.
Today at Internet Week in NYC, we announced the provision of Expression Studio 4. You can download the trial of Expression Studio 4 Ultimate that also includes Expression Blend 4 and SketchFlow by clicking below:
Keep watching this web site for more news, updates, and in-depth investigates some in the new features that weve introduced. Until then, here are a few related links:
Note that if that you are currently doing Windows Phone development, please not upgrade to a final version of Expression Blend 4 yet. We will release an new version of all individuals phone components from the future, so please keep using Expression Blend 4 RC.
Of course, no major release could well be possible with no feedback all of you could have provided, so thanks!
While the PathListBox control offers an easy way to formulate items along a path, setting up a carousel control that appears 3 dimensional and possesses smooth scrolling requires additional functionality we did not have the perfect time to do in Expression Blend 4. Ive came up with the PathListBoxUtils sample positioned on CodePlex to produce the tools that make setting up a carousel just like the one shown below a breeze:
Visit the Carousel tutorial to discover how to build this example, and you are able to view all PathListBoxUtils-related tutorials here.
Its been a little while since the last article where I promised to post about all in 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 as well as the StoryboardCompletedTrigger.
Storyboards are one from the primary ways you create animations in Silverlight, WPF, and Windows Phone using Expression Blend. Creating a storyboard is very easy, truly using a storyboard like having it play isn't. To help on this, you've got the ControlStoryboardAction.
Simply put, the ControlStoryboardAction can be an Action that allows someone to select a storyboard and specify what we would like to try and do to it:
Lets check out some with the properties its content has in greater detail.
When you are looking at this behavior, you will 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 need to play a storyboard, stop it, toggle between play/pause, pause, resume, or jump on the end.
The only missing piece thus far is knowing which storyboard to affect. Not to worry, as you specify the storyboard while using the aptly named Storyboard property:
This property are listed all from the Storyboards your behavior has access to. Once you've got selected a Storyboard, you happen to be done!
This trigger invokes an Action every time a specified storyboard set through the Storyboard property has fully cost completion. Of course, because it is really a trigger, you are able to use it with any Action.
In Expression Blend 4, one in the new samples we added is known as MockupDemonstration. If you havent experienced a chance to utilize it yet, you may open MockupDemonstration through the Welcome screen, that is available once you first start Expression Blend or whenever you click Help and after that click Welcome Screen. In the Welcome screen, click Samples, then click MockupDemonstration:
As you'll be able to tell quickly from exploring this sample, this sample boasts a handful of controls designed to aid you create prototypes easily. The catch is these controls only exist in this particular sample. Since some of you might have requested that it could well be useful to own these controls available outside in the sample, this writing will explain how for making these mockup controls accessible 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 on the pre-configured Libraries folder through using the steps below:
1. Copy both and Design folder from:
for WPF projects, follow this but copy files from Libraries Debug
2. Add copied files to your 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 inside previous the answer to Libraries 4.0
3. Restart Blend. You can now adapt mockup controls by clicking the Mockups category from the Assets panel the suitable assembly reference is automatically included with your project.
If you've any questions or comments, please you can post below or on our forums.
At MIX, we released a beginning preview in our support for building applications for Windows Phone 7 that only ran on the pre-release version of Framework.
If you could have been delaying on upgrading to your latest versions of Expression Blend, Visual Studio, 4, wait forget about! Today, we in conjunction with the Windows Phone team are releasing an update to your components we released a few weeks ago to work on a final version Framework 4.
Besides the RC posted above, you'll need the following components installed for developing Windows Phone apps:
Besides support 4, there has been some general improvements towards the overall design experience, emulator updates, and breaking API changes. You can get a broader overview within the Windows Phone Developer blog.
As always, we enjoy hear from you. Please you can comment below or use our forums here.
As the vast majority of you know, yesterday we released the production candidate version of Expression Blend 4. Shortly after a lot of you stood a chance to spend playtime with it, many of you reported that Expression Blend crashes during launch.
If you might be one of those people whose Expression Blend crashes after launch, please download this minor revision from the release candidate we released a couple weeks ago:
If you arent having any problems launching Blend, you don't need to upgrade. There are no the latest features or changes besides some changes for making sure Expression Blend runs properly on launch.
We were capable to detect this matter thanks largely with the error reports those of you using this type of crash submitted. We constantly undergo all with the crash reports we receive, so we try to fix as a lot of them as you possibly can.
While produce your own . you never need to experience crashes from running Expression Blend, should you choose experience this brief, please submit larger than fifteen reports!
Recently, a final versions of both Silverlight 4 4 have already been released! To coincide using this, we have been releasing a release candidate version of Expression Blend 4 that it is possible to use to concentrate on them:
There are two things that you simply really need to learn about this release.
First, if you happen to be doing Windows Phone development, you must not 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 relieve Expression Blend 4 targets the last versions of Silverlight 4 4, you may share your creations using the rest on the world. You no longer are restricted to only sharing your creations in source code form or private testing.
If you havent stood a chance to browse the sessions from MIX10 that showcased Expression Blend 4, backlinks below should assist you to 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 on the sessions from MIX must be available online, so head over to your MIX Sessions page to look at more: /Sessions
Click here to see Kennys MIX 2010 session that covers a lot with the topics you see in this article.
In Expression Blend, weve been thinking for the loooong time about how to create it ever easier to generate great animated visual effects quickly on top in the Silverlight and WPF runtimes. Weve been investigating large-scale animation needs since Blend 2 SP1 and steadily building features to deal with those needs, and now we think weve reached critical mass. With Blend 4, we've got a compelling pair of technologies that really work very well together.
This blog post can be a companion towards the Dynamic Layout and Transitions demo app that weve placed within 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 begin specific particularly that here, it forms the foundation for all the options described below. Some of strikes work right from Storyboards you create among others create Storyboards behind the scenes in your stead and sometimes both.
Lets begin with turning the hands of 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 using the WPF Toolkit. This introduced the notion of the state being a means of communication between visuals and code, and created it dramatically much easier to describe a group of visual changes. Based on input, the control code could decide when you should enter what state, as well as the visuals would decide what changes were contained in that state plus how much time it latched onto transition between any couple of states it's advisable most state changes to consider 0.25s, but want Pressed state changes to become instantaneous.
This proved to be an extremely effective tool, but it really had limitations. The core VisualStateManager runtime which well call VSM down the road could only do linear interpolations in the values being set. This is very rewarding for opacity and transform offsets, but doesnt work effectively for discrete properties or data that isnt known until runtime. Also, you cannot assume all animation scenarios are on the odometer by state changes. So we put our thinking caps on about precisely how we could find more scenarios to be effective in a way that designers could rapidly tool the consequences.
In V3, we added four primary enhancements of this type. The first was EasingFunctions, which might be critical to making property animations develop the right feel. Weve got all of the classics quadratics, cubics, bounce, elastic, etc. Plus, you'll be able to write your personal EasingFunction in C or VB and use it to any animation you would like. This is all supported in Silverlight 3 and WPF 4. EasingFunctions is usually applied for an individual animation or keyframe, and you'll be able to apply a default EasingFunction for your entire state transition.
The second would have been a GoToStateBehavior together with Blends Behaviors engine, which made it all to easy to program your complete state change logic directly within the markup without code. Like all of Blends Behaviors, you'll be able to simply drag it from my Asset Panel onto any elements you decide on.
Those two enhancements just made the present scenarios run better. We also wanted to treat new classes of scenario. The first one we tackled was the matter of elements transferring a StackPanel or WrapPanel. Traditionally, these four elements have snapped into place being an application changes elements or changes size, and now we wanted an even transition that users could control. So we introduced the FluidMoveBehavior to produce it simple for an element to observe the layout manager whenever it gone to live in a new spot, and erase its progress having an animation controlled by some of those EasingFunctions we described earlier. So now its an easy task to have your elements animate into place at the speed you ultimately choose!
Heres a picture from the feature for action. Theres no longer room around the first line for your purple rectangle, so its moving towards the beginning in the second row plus the other elements are moving to produce space. Technically, coming from a layout perspective, the next thunderstorm in motion have been at their destinations already but by adding the correct transforms ahead, we have the change look smooth in the visual perspective that users cherish.
The fourth enhancement we made was essentially the most challenging for people. We realized that many times, customers wanted different states of their control to own different layouts entirely, but nonetheless respond to active layout changes within the application. For example, one layout probably have a list of task panes visible beyond your working area, and another will often have one or more of those panes hidden. Customers needed to describe these different layouts with states to acquire a good separation between their visuals along with their business logic, though the properties that was required to change between these states werent properties that may be smoothly interpolated. For example, how will you interpolate between and?
What we learned was that within the like these, users werent satisfied while using direct property animations our system as long as they just wanted it to check right, and which makes it look right required that people animate a morph on the change instead of the change itself. So we wrote a train locomotive that would require a layout snapshot ahead of the state change, take another layout snapshot following your state change, and create an even morph involving the start and end positions, employing the duration and EasingFunction on the users choosing. We dubbed this FluidLayout, and you may turn it on here:
Just click that little button, and your entire layout alterations in that VisualStateGroup will probably be animated between states regardless of whether it seems impossible. Well even simulate a Visibility change by using an opacity simulation. Note that youll have an overabundance success when you click this before starting making layout changes otherwise, if you move something, itll create translate/scale animations that do not respect layout, because thats the most effective that the conventional VSM is capable of doing.
Its hard to accomplish justice to the feature in images, but heres my best attempt. In it, the Timeline Pane is inside the process of shrinking for the leftmost column, which I configured by changing the Panes property inside a state. Similarly, I changed the RowSpan on the pink rectangle, and it is inside process of skyrocketing taller being a result.
In Blend 4, weve managed to adopt these themes farther, and also have three more toys for designers to have fun with. Lets start with animating things in and out of lists. In V3, you may apply a FluidMoveBehavior for a ListBox, along with the other items would dutifully make room to your new item or close the space. But there wasnt any easy way to effectively control the item that has been itself being added or removed; in case you were clever, you may rig up some events to produce an element animate on entry, therefore you had being really really clever and pollute important computer data model in unfortunate ways to generate an element animate on exit. We worked closely while using Silverlight team to make a solution here that you'll be able to tool effectively, and its particular called LayoutStates. To find them, first edit the ItemContainerStyle:
And then, note these three new VisualStates inside the States Panel:
You are able to use these states to model what an element seems as if just before its loaded, what it appears like after its been loaded, and what it seems as if just before its unloaded. Silverlight might animate their state changes for you with the appropriate times, when your items are combined with or removed through the list. Remember to convey a FluidMoveBehavior on the ItemsPanel template note its presence within the Edit Additional Templates submenu, a few pictures above, as well as set AppliesTo Children, to get the other components to move out from the way. Note when your ItemsPanel is usually a VirtualizingStackPanel, your ListBox ought to have set to Standard, otherwise you should learn one in the other new tricks below.
Heres among this for doing things the middle item is simply entering a list.
The next feature we added is another from the vein of simulation. In V3, we added FluidLayout to VSM in order to get an even and realistic morph between two states, nonetheless it got us to thinking concerning the other sorts of morphs we might perform. Enter TransitionEffects. Whereas transition effects in video editing offer a pixel-based transition from a single video clip to a different, Blends TransitionEffects offer a pixel-based transition in one state to a different. In Blend, a TransitionEffect is usually a PixelShader that's an animatable Progress property. We are shipping several of such in our SDK, and if you recognize HLSL you may write your. Heres the way you set one up:
As configured here, all state changes from the LayoutStates group will do a Smooth Swirl Grid pixel-based TransitionEffect, taking one second sufficient reason for a cubic ease. You can needless to say set some other transition for almost any individual state change if desired. Some in the TransitionEffects have properties to help promote customize them; one example is, Smooth Swirl Grid allows you to control the quality of subdivision plus the intensity from the twisting effect, but those properties are under the combo dropdown inside the picture. Heres a screenshot of these TransitionEffect in working order:
The final feature we added is one thing that weve been wanting to wrap our minds around for 5 years. Weve remarked that in lots of applications, visuals will move from a single part in the application to a different even though the visuals in many cases are generated from data. In a true MVVM design the location where the data model ought to know nothing concerning the visuals, its extremely hard to get these types of effects.
What weve done is train the visuals to learn more concerning the data model specifically, to practice FluidMoveBehavior to associate positions with data rather then with visuals. This wants a little bit of explanation, but is remarkably very easy to use you are able to create an animated list-detail example on your own in about two minutes.
What we'd like is for your large chair within the details view to seem to grow out with the small chair within the master list. All we've got to do is locate the Image element within the ItemTemplate for that ListBox, and offer it a FluidMoveTagSetBehavior that could register it using the FluidMove system. That appears like this:
Note how the Tag property shows that element will likely be tagged based on its DataContext, and that is the model item behind the visuals. Next, theres a FluidMoveBehavior within the detail Image, which seems like this:
The other half in the connection is made using the InitialTag field that's set to DataContext. This means that once the detail element appears, it is going to consider the registered position of the company's DataContext to get the place it's going to appear to result from. And thats everything! Heres a screenshot of these app for doing things; be aware that in this case I set the FluidMoveBehavior for the entire Grid, so how the details would animate in conjunction with the image.
Theres a great deal happening behind the scenes, but weve was able to boil this complex scenario to the telltale two simple properties. This system can be used to animate objects from a single list completely to another list.
If I had included all in our future investigations of this type, this post would be two times as long because it is already. Were working hard to treat more and more scenarios inside simplest ways possible. Rest assured that the information hearing about more improvements someday inside not too distant future!
If you could have any opinions or feedback, please twenty-four hours a day comment below.
Architect, Expression Blend
As many of you understand, today was day one of MIX - Microsofts annual conference for designers and developers. Just like previous years, there has been plenty of great news coming out from the conference.
The two big things we announced are Expression Blend 4 Beta along with an add-in to Expression Blend giving you to be able to build applications for your Windows Phone.
Christian Schormann incorporates a nice summary of Expression Blend 4 and the extra features in it, so if you need to learn more, go read his post.
Of course, there will probably be plenty of posts within the upcoming days and weeks that dive into detail on the weve released and announced today, so stay tuned for more.
Over your next couple of weeks, it appears like smart to go over some with the behaviors we shipped to be a part of Expression Blend 3. Many of you could have mentioned that you just would like to learn more around the stock behaviors we ship and the way they are used, this blog will likely be a good interim solution with the until we properly incorperate your feedback into our future product documentation.
First through to our list is a of one of the best behaviors that any of us shipped, the GoToStateAction!
As you understand, you might have the capacity to define and modify your visual states within your applications:
Having a visual state is only 1 part of the needs to get done. The other part will be being in a position to switch towards the visual state in the appropriate time. For predefined visual states that you just find with your controls, the mechanism for switching states is constructed in. For visual states that you simply create on your personal, you will have to deliver the logic for switching the visual states yourself.
That is when this behavior can be purchased in. The GoToStateAction allows you to definitely easily switch visual states given the right event using just your Properties Inspector. The following screenshot explains the standard behaviors UI customized while using properties exposed by GoToStateAction:
Lets look at a few 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 with the various properties in greater detail.
The visual state is set using the StateName property. By default, you will see all of the states defined within your root scope ie: UserControl or Window irrespective of 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 focus on another element, such being a Button containing its own states, the StateName list is populated with those states instead:
I spoke lots about changing the target that your particular states result from, so lets look for the TargetName property the spot that the element you desire to target will be specified.
If you would like to target states that reside somewhere else for instance another Control or UserControl, you may use the TargetName property to customize the element you wish to point to. As mentioned earlier, the default value for TargetName will be the root scope like your UserControl or Window.
If that you are trying to choose something that isnt easily selectable visually, you may hit the limited button to determine a flat listing of the of your elements. That is similar to whatever you see within the Objects and Timeline panel.
You may switch states suddenly, or it is possible to smoothly transition into states. The UseTransitions property is what controls what your behavior is going to do. By default, the UseTransitions property is checked, but you'll be able to uncheck it in the event you want a sudden switchover for your new state.
Hopefully this helped provide a summary from the GoToStateAction and exactly how it might be used. If you've any questions, please go ahead and comment below.
For a restricted time, there is really a 30% discount on all Microsoft Expression 3 products Microsoft Expression Studio Expression Web, both full and upgrade versions throughout the Microsoft Online Store for US-based customers:
No promo code required in any way just see a store and add to your shopping cart!
Ok, pop-quiz time. Below, you'll find two screenshots I took from two different applications:
Can you tell precisely what is different between the above images? If you said how the button within the second image seems some pixels off on the image within the top or something similar, you might be wrong. The UI depicted in both with the screenshots is likely same. Yes, it was obviously a trick question.
While both applications look almost the identical when run, let me detail both of those applications when opened in Blend. Here is what the application form depicted in Screenshot 1 appears to be:
As it is possible to tell, there is often a major discrepancy involving the first and second screenshot when viewed in Blend. More specifically, the next version with the application seems for being missing some UI plus the button isn't styled whatsoever.
The source with the discrepancies have to try and do with what Blend actually shows for the design surface. By and large, Blend is often a XAML editor. Anything defined in XAML, we'll do healthy to display it on our design surface. For visuals defined within your code-behind files, may very well not always be capable to see them in Blend.
This is the spot that the differences relating to the two apps comes from. In the first app, everything was defined in XAML. In the 2nd app, some from the visuals were defined in XAML, but a many in the visuals are not. That is why Blend is showing an incomplete subset of what the job actually seems like when you view it about the design surface. This can be a problem.
The word problem might be a harsh word because of this, though the outcome is lower than ideal should your application is often a collaborative effort between someone technical and someone less technical. If you're a developer, being capable of visualize code and produce changes can be straightforward. If you happen to be more design oriented, considering code to define the appearance and feel of your application will not be natural. You would prefer something that seems like the application depicted in Screenshot 1 where things are all exposed in Blends design surface and you are able to make changes visually without writing code.
The first and obvious answer that I have is to possess you subdue the longing to add controls, define layout, or perform other visual tasks using code. The reason is the fact, while you saw within the screenshot on the second application, Blends design surface wont be able to help you you out.
Of course, you can find many times when such an extreme solution will never work. It is common for many people applications to get into a gray area where visuals are partly defined in XAML and partly defined in code. Fortunately, you can find some simple steps it is possible to take for making designers more productive while still giving developers the pliability to develop the applying.
If you might have visual content that needs for being added programmatically, be sure that content is looked as UserControls. The reason is that you may define the UserControl making changes entirely within Blend. Programmatically, you may add this UserControl which can have been edited inside Blend to the application without sacrificing the designability on the UserControl itself.
Create Styles in XAML, Apply them Programmatically
Sometimes, UserControls could be a bit excessive. For example, within the second screenshot, I have a button that may be unstyled:
Instead of developing a dedicated UserControl to wrap your styled button, you can just define the form in Blend and programmatically apply the design. Lets say you've got a style called GreenButtonStyle defined within your Resources panel:
To apply this style in your button, use the next code: