On our developer machines, we have Silverlight 4 installed. We upgraded to VS 2010 SP1, and now our Silverlight projects won't open; it is prompting us that we need to install the newer version of Silverlight, and takes us to a link to download Silverlight 5.
We are not ready to go to Silverlight 5 yet, and need to be able to open up our Silverlight 4 projects in VS 2010 SP1.
Any suggestions?
This sounds like it may be a duplicate of this question, but since you say you had Silverlight 4 installed before it may not be.
I recently rebuild my development machine and ran into a similar problem, but closer to that other question. Ultimately, I found this blog post, which led me to a installer for Silverlight 4 Developer Runtime.
There was one issue the author mentioned, that I have not run into yet:
I have noticed a large number of people hitting this page. Well,
let me help you guys out a little more. It turns out that EVERY time
Microsoft decides to update the Silverlight runtime. A patch, string
change, someone looked at it wrong, the Developer runtime gets
invalidated.
You will need to reinstall it each time. So make sure you keep it
handy! Thanks Microsoft for such a wonder feature. I love reinstalling
things every week.
EDIT:
I ran into the issue mentioned above and reinstalling the Silverlight 4 Developer Runtime did not fix the issue for me. I ended up installing the Silverlight 5 Developer Runtime (32 bit, 64 bit), which I obtained from this page, and that fixed the issue.
Related
I updated Silverlight on my dev. machine, but clients still have older Silverlight version and they do not want to update.
Now I need to revert Silverlight 4 back to older version (50401). I tried to uninstall Silverlight and install older version, this required my to install developer tools, too.
No luck, still it requires newer version on clients machines. So I suppose real version is inside developer tools?
The question is, how do I make VS2010 to compile project for specific Silverlight 4 build?
I already stumbled on that kind of problem, and I had to re-install my sdk.
Check out that great article from Tim Heuer:
http://timheuer.com/blog/archive/2010/09/28/keeping-your-silverlight-dev-environment-stable-through-service-releases.aspx?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+timheuer+%28Method+%7E+of+%7E+failed+by+Tim+Heuer%29
Good morning fellow stack overflow people, I have a question that sounds like the start of something from the daily wtf.
The company that I work for is not so much sacred of new technology they just seem to let things slip, you know the type, “It worked 5/6+ years ago so I don’t see why we should change it”
Despite this I have managed by hook or by crook to get an installation of SQL server 2008R2 to develop on which has the reporting services. Excellent I think, I can finally start moving some of the access applications to VB.net and use SSRS to provide some embedded reports, everyone is happy.
But not so fast, it turns out the standard build of desktop here only has .net1.1. I have managed to dust off a copy of visual studio 2003 (The last edition that could target 1.1) and built a few little tests to check DB connectivity. The problem I am having is the report viewer control is only available in .net2.0 and above.
So what options do I have for displaying my SSRS reports in a VB.net1.1 thick client application?
Before anyone asks the following options are out
Going anything web based (Farrrrrrrrrr too modern for the company + no web server)
Upgrading to a version of .net released after George Bush the 2nd lost an election but still became president
Changing jobs
Sorry for the long question but I thought some background would help
I would go for a browser control but I think they only started including that in 2.0. But I think you can still do something like that in 1.1 (it has been to long to be sure).
I think if you install SSRS on the sqlserver you could turn on IIS on that server and then use that to make your reports and show them in the browser control.
SSRS (I'm pretty sure it came out somewhere around 2005) is not old enough to have many other options.
If you work with VB.NET 1.1 all the time then it is strange question. How did you program in it before?
Use any available dataview control (I already do not remember - DataGrid, DataList, Repeater) from .NET1.1. There is nothing in ReportViewer that could not be done before its appearance, in .NET1.1.
What is the problem?
Update:
I remember seeing code projects reproducing ReportViewer in .NET1.1 few years ago though I cannot find it now. Anyway, it seems to me the problem of just reading .NET1.1 docs and searching internet.
Sorry if this is a blunt statement but sometimes, you've got to bite the bullet and do the right thin.
If you really want to use reports and you've found the minimum version of the .NET framework is 2.0 then go ahead, find an internet connection somewhere and upgrade the computers.
If you can't do that, forget about it and go back to your VB6 or whatever you're using. Besides, .NET Framework 2.0 sp1 is less than 30MB. If you can't find a decent internet connection (either at your workplace or somewhere else) to download it then you might as well abandon it.
And I'll add as well. VS2003 IS OLD! Get yourself minimum VS2005, even if it's Express edition, it's good enough and stop whining.
Someone had the same question back in Feb. Maybe this might send you down the right path:
Using SSRS in ASP.NET 1.1
I had VS2010 running fine with Silverlight development. Then I installed Expression Blend 4. Now when I run VS2010 and try to debug a silverlight app I get an error saying "Unable to start debugging. The silverlight developer runtime is not installed. Please install a matching version." I've tried uninstalling silverlight tools, and reinstalling them from scratch (the latest april version). But I still get the same message. So basically I'm now unable to do VS2010 SL development. I'm on the verge of just rolling back to my last system restore point and giving up on Blend. But if I do that I'd be worried that Product Activation would never allow me to reinstall it in the future, since the MSDN download page implies I'm only ever allowed to install it on a single machine. Any help appreciated.
Thanks
I had the same problem after installing Expression Studio 4. I installed the Developer version of Silverlight at: http://go.microsoft.com/fwlink/?LinkID=188039
and the problem seems to be resolved.
Hope that helps.
Try reinstalling or reparing the Silverlight_Tools for Silverlight 4.
You tried that.
The product activation system isn't that draconian it has to allow for things like hardware failures etc which would require re-installs.
Thanks for the suggestions. I solved it this way: Since I'm running under parallels, I rolled back to a snapshot taken before I'd installed Blend. Then I rebooted Windows. Then I reinstalled Blend (happily with no draconian activation problems!), and everything worked.
So why did it work the second time and not the first time? The first time I installed Blend, I'd shut down VS2010, explorer etc, but not rebooted. Perhaps some hidden VS-related process was still running. Installing Blend in that situation screwed everything up, and removing and reinstalling stuff didn't fix it. Obviously the Blend installer should have spotted the dangerous process and taken remedial action, but it didn't. Perhaps MS recommends you reboot before installing new software? That would be a bit of a nuisance, and I've never needed to before. My real lesson from this is to work in a VM and take regular snapshots.
Thanks again.
As probably everyone knows, MS just released the RC for Visual Studio 2010 (http://msdn.microsoft.com/en-us/vstudio/dd582936.aspx). I'm about to download and install it, but I need to know if the current Silverlight 4 beta bits are supported. Anyone happen to know, or know differently? (If I don't get an answer, I'll post my results back here.)
ScottGu tweeted: "Support for Silverlight 4 with the VS 2010 RC will show up with next public SL4 drop (and so is not yet enabled with today's bits)". Next question is when SL4 bits will be refreshed...
I cannot open a sl 4 beta app in vs2010 rc. Hopefully they will update the sl 4 beta soon
There is a workaround to this now:
http://translate.google.com/translate?hl=en&sl=auto&tl=en&u=http://sorokoletov.com/2010/02/hate-2-wait-silverlight-4-beta-2-vs-2010-rc/
For sure not everything will work, but it is beta and thats fine. I like many others don't have a second [fast] spare machine to run VS2010 Beta 2 on just to be able to continue using it.
I can confirm it will compile and run an app which is right now a lifesaver to me.
Issues I've found :
Cannot seem to use dynamic keyword even in very simple cases.
dynamic foo = 12;
dynamic bar = 2;
var total = foo + bar;
One or more types required to compile a dynamic expression cannot be found. Are you missing references to Microsoft.CSharp.dll and System.Core.dll? (yes I do have these DLLs and yes they are the silverlight 4 DLLS)
PLEASE ADD ADDITIONAL ISSUES TO THE COMMENTS
I noticed a few tweets this morning about a new version of Silverlight having been released - Silverlight 2 GDR 1 (2.0.40115.0). Details of what/why/should I target it/is it backward compatible/etc seem incredibly thin on the ground.
Hitting this Silverlight page on Microsoft.com tells me my version (RTW) is now out of date and I should upgrade to GDR 1. But hitting silverlight.net - there's no mention of it, the Silverlight elements on the page don't tell me my version is out of date and the Getting Started page still links to RTW tools.
This kinda leads me to presume that if you upgrade your dev tools to target the GDR release, then your users will need to upgrade their Silverlight install also?
A few details on what's in GDR can be found in the release notes - but it sure would be nice if Microsoft would clarify it's purpose and suggested adoption. Anyone got any more details?
Tim Heuer explains all: http://timheuer.com/blog/archive/2009/02/19/silverlight-2-gets-minor-update-gdr1.aspx
It seems to be only bug fixing.
So if your applications (so your users) are not concerned by those bugs, it is not mandatory to update your plugin for the moment.