I didn't find out about this until I already upgraded VS2010, but according to Visual Studio Magazine :
In VS2010 Beta 2, many developers
reported issues when working with XAML
and Windows Presentation Foundation
and Silverlight. The VS2010 RC
supports Silverlight 3.0 apps.
Silverlight 4.0, still in beta, is not
supported in this release.
"We will be adding VS 2010 RC support
for SL4 with the next public
Silverlight 4 drop," explained
Guthrie. "If you are doing active
Silverlight 4 development today we
recommend staying with the VS10 Beta 2
build for now."
Being a developer, the paranoia set in....
Anyone know of any red flags or known issues to watch for?
Some of our developers have reported a high incidence of crashes working with Silverlight 4 in VS 2010 beta2.
One thing that helped was to view XAML in XAML mode not Design mode.
We also have seen issues using Blend in conjunction with VS 2010 beta2 as it can't handle solution folders.
FYI, the app crashes at least twice a day for me. Not all occurrences have been consistent. Those that were have been reported or previously identified. The main two that tends to crash it is switching between the XAML/Design view or attempting to deal with/switch back and forth between two instances of VS2010 open on the desktop at once.
Suggestion: Save and save often.
Related
Our version of Microsoft Expression Blend Preview for Silverlight 5 has expired on 30th June and there are NO online license purchase options available.
The following link states that Blend is now an integral part of Visual Studio 2012, but with our current constrained development and release cycle we do not have the option to upgrade our entire enterprise class application to VS 2012. So, my questions are:
Can Blend (Preview for SL 5) licenses be purchased online? If yes, where?
If not, then how can we continue our Blend based development without upgrading to VS 2012?
Unfortunately, Microsoft left us down.
The only option is to go with Visual Studio 2012, as it includes Blend with it, but bear in mind, it is not smooth, buggy and crashes more than the Preview version for Silverlight 5.
I've even created a bug report on Microsoft connect, which was deleted strangely by microsoft.
PS : I tested the Update 1, Update 2 and Update 3, all of these on solution containing work done in silverlight 5 and telerik controls. It takes 15 minutes to open, and then crashes, this issues was not detected on Preview Version
For Now, We are changing the system date to a date before June 30, Open Blend Preview, and then fix again the system date (because if you don't, you will have nightmare with Skype and outlook :) )
I'm currently using Microsoft Visual Studio 2010 for school. I recently completed a project for the Window Phone 7 platform and am now working on an XNA3D project, however I cannot seem to change my SDK environment from WP7 to XNA.
I've opened previous projects that were started using the XNA framework, but Visual Studios opens using Windows Phone 7, not XNA. I've tried creating a new project and creating it as XNA 4.0 but when Visual Studios loads up my workspace it is still using the Windows Phone 7 header in the drop down menu at the top of the screen. The program still loads the required XNA framework, and will run my program as XNA and will not load the Windows Phone 7 Emulator, so it's not a massive in-my-face kind of problem, but it is an annoyance, and one that neither myself, nor my teacher can solve. I've played around with some of the settings and properties but nothing seems to change it. VS2010 won't even let me click the drop down arrow and select XNA, it's greyed out.
What I'm asking, is has anyone encountered this issue before, and if so, how did you resolve it? Or, do you know how I can fix this and get on with my homework?
Visual Studio identifies the project with unique projectID. And I guess this is the case for you. I highly recommended that you should update the visual studio to 2012 it is good and you can use XNA there too. Here is stackoverflow question explaining details. And it may solve your issue too.
And there is one more way, you can create new XNA project and link your all files to that project. Most of the things works there. Normally I do that while creating [Monogame] (http://monogame.net/) A nice opensource port of XNA.
I hope I understand your question correctly and able to answer that. Please let me know if any specific or more details required.
I have installed VS 2012 some days ago.After activation there are some strange lines in the UI
that appear on menu and code editor area.I don't know how to get rid of them.
http://mojoimage.com/free-image-hosting-11/4739vs2012.png
another example while repairing VS : Picture
VS2010 and 2012 use WPF for their UIs - it's likely this issue is with your graphics card or driver. Please ensure you're running the latest graphics driver versions. If the issue continues then I suggest you try running other WPF applications and seeing if they render things okay.
I am using VS2010 ultimate Beta2 and under Visual C# -> Workflow -> I don't see the Sequential workflow console application or state machine console application
Could someone please advise why these are missing in VS2010. I am able to see them on VS2008 ->Workflow.
Thank you
In VS2010 Pro RC1 the sequential workflow console app and state machine workflow console application are only available if you choose .Net Framework 3.5 in the combobox above the project types.
But why worry about beta 2, now that RC1 is out?
I would think that if this is a true and serious error, a bug report is probably better than a SO question.
As Guge says this is by design (It's the same in Beta/RC or RTM). In Visual Studio 2010 you have 2 different versions of Windows Workflow. The new one (4.0) uses a new runtime under the hood and has a WPF look and feel. The designer/activities are different.
The old one (3.5) -also called Legacy- can only be created in Visual Studio 2010 if you change the target framework to 3.5 or 3.0. After you do that you will have the option of State Machine/Sequential WF Console App.
Note however that after you have created the 3.5 workflow you can retarget to 4.0. This will keep the same designer/runtime but it will be running under the 4.0 Framework. Everything will work as expected.
If you try to upgrade and existing VS2008 project you will get the option of doing this.
I'm about to start a new WPF project and there are a number of things in 4.0 that I need (multitouch for one). I've heard that VS 2010 beta 2 will be released at PDC in November so I'm considering starting the project in beta 1 now, then migrating to beta 2 when it becomes available. Assuming I only need to live with the environment for about 3 months would it be reasonable to start this project in VS 2010 beta 1 or is it not ready for daily development?
I'm not sure you're going to get the answer you're looking for here. In part because it's really hard to understand what you mean by "ready".
Visual Studio 2010 Beta1 is a beta product and hence will have beta issues. It will crash more often, have more performance issues, less features and generally speaking not as smooth of an experience as an RTM product would. That's essentially the definition of a beta.
But is it ready? I use it on a daily basis at home and work for essentially every project I work on (including those which ship on the 2.0 or 3.5 framework). Yeah I occasionally run into some annoying bugs. But nothing so severe that I stopped using the product.
I've been doing a few things myself with .NET 4.0 recently, nothing major or for production, but it seems stable enough.
Though others may have had a different experience to me.
As it's beta software, I wouldn't recommend using it for Production purposes until it's fully released, or at the point of RC.
However, like I say, it seems to be stable enough in the .NET aspect of things, but I've not tpyed with WPF 4 yet so I would leave that decision up to you.