Bit of a random one here, and I've exhausted my knowledge on how to try and remedy this.
Basically I've just switched out my hard-drive over to an SSD (best move I ever did), and along with this I've had to reinstall everything from the ground up. When I've done so however VS2010 Express for Windows Phone keeps giving me this error with my existing projects(Silverlight 4 SDK is not installed + bunch of warnings).
But I have made sure it is installed
I have gone through reinstalling the Silverlight 4 SDK, uninstalling all of Silverlight + VS (and all it's many, many components in Control Panel) and performed updates via Windows Update, rebooting etc. Nothing seems to work.
Strange thing is though, if I create a new project it works just fine, no warnings, no errors, nothing. I'm completely stumped.
Any ideas guys?
My usual install process is:
Silverlight SDK > VS2010 Express for WP7 > Begin Developing
I have deleted the .suo/.user files, also the obj and Bin directories too. No avail :(
The only thing really that has changed since my last install was the directory I am loading the actual projects from (but I don't see how this could affect it?).
I wasn't able to solve this one without performing a full reinstall. I did discover some other elements of Win32 applications having issues as well, seems my Windows install was simply broken.
Related
I'm working with an old (Delphi 2010) app with a number of very specific components that have to be installed, some from compiled from sources. It's a pain to set up, is what I'm getting at.
Currently, I have it on a Windows 10 machine, but I haven't upgraded Windows 10 in quite some time. If I upgrade Windows, it breaks the debugger (and I haven't been able to fix that so I've downgraded Windows).
I'm trying to find any way to move the Delphi environment without having to go through the various steps to get it to work, like making a VM out of it. Or, if I have to go through the steps again, only do it one more time in such a way that I can push-button recreate it. (There are a lot of things I need to try to upgrade the app itself, but many of those strategies will break the environment for me.)
Any strategies?
I know, there are countless threads about this control already and I've been reading them for hours. I can't add get this ocx to load into VB6, running 64 bit Win 7.
Things I have already tried:
1. unregistering and re-registering (used regsvr32 from syswow64)
2. Did the regtlib msdatsrc.tlb thing I've found
3. Reinstalled sp6
4. Installed the cumulative update everyone is saying is the latest version
I haven't reinstalled VB6, I don't have the media at work or I would have, but this has shown to never be the solution to this problem on the successful fixes I've read about these past few days I've been working on this.
Things to note that people aren't talking about in the other threads: I can add the ocx to Office without issue, then add controls (treeview, imagelist, etc) and use them fine. I can't add the OCX to a new, empty VB6 project. Most users are trying to open existing project, which fails for me as well, but never say whether they can add the OCX to a new project. I can't.
I hate to create another one of these threads to further muddy the water, but the solutions in other threads haven't been working for me and no one is mentioning where they can add it to Office or a new project.
This used to work fine months ago, too many things have happened since then to be able to pinpoint one that may have caused this. My main focus is to be able to add it to a new project again.
Thanks.
EDIT:
VB is being run in elevated XP SP3 compatibility mode.
Found the solution. I don't know how it came to be, but I had 3 different versions registered in my registry. Maybe the version that was trying to be used by VB wasn't compatible but was compatible with Office? I don't know.
Here's what I did.
I opened up the registry (regedit.exe) and searched for the key 831FDD16-0C5C-11D2-A9FC-0000F8754DA1 and found the three different versions were listed. I made a backup of the sections I was going to change, of course, and then just deleted all of the version entries. After that, I went back and registered what I had in my syswow64 directory and now it's back to normal. Rechecking the registry shows I now only have version 2.2 installed.
This may be trip down memory lane. I have been asked to fix some code that was written 8 years ago. That in itself is OK. I have a Win 7 64 bit PC. As I now use VS2012 I had to install 2005 luckily had a copy still. Then all the updates from MS so that it will work with Win 7 64 bit. Create a dummy MFC app to make sure it all works. So far so good. Next I get the SDK to target the code to it is running on a Moxa UC7124 ARM4i. I get UC712XCE_SDK_V2.0.msi and install it.
Now the problem starts. I cannot see the Moxa platform inside VS2005. If I load the solution it comes up with the platform but skips compile. My guess is that VS cannot find the SDK. I have tried many things but obviously not the correct thing yet, I checked for environment variables and find none, registry has no entries.
I look inside Tools | Options under Projects and Solutions VC++ directories but cannot find the platform I only get Win32. So for the first time in a while at the moment I am lost. Has anyone got any ideas why I cannot get the Moxa SDK visible inside VS2005?
After several days progress has been made ....... but not yet fully working. My view was that there must be some permissions issue in Win 7 when trying to load older SDK's, so I uninstalled the SDK first. Next I right click on the SDK's msi and in security tick "run as compatibility" and choose "Previous version of Windows". I can now target my solution correctly. So this part appears to be working now and next I have to fix all the compile/linking issues. Still got a big hill to climb but fingers crossed when I get to deploy this that it is all going to work OK.
I have been searching for the answer for this for 2 days. We have an application that uses ReportViewer 9. However, clicking on the print button in IE10 causes the browser to stop working (with the "Debug" or "Close Program" buttons). Everything else seems to work fine.
We tried using ReportViewer 10 but we get the same issue.
We are using Visual Studio 2010, Windows 7, IE 10, and targeting .NET 4.0. The crashes happen in the IDE and through IIS.
EDIT: Things I Have Tried:
I have tried adding my website to Trusted Sites, lowered the security setting, and I think I've tried every possible combination of checkboxes in the "custom" security box.
I've tried enabling Protected Mode and Enhanced Protected Mode, with a variety of check box combinations from Custom security level that sounded promising.
I've tried forcing IE10 to run in 64-bit mode (including the tabs), but our app forces the tab to run in 32-bit anyway.
Someone suggested that it might be a Kill Bit issue, so I tried editing the registry to ignore kill bits just to see if it would work (it didn't).
Also, I'm pretty sure I've tried just about every permutation of all the variables I've already mentioned. (I'm a little burnt out at this point, so I might have missed 1 :S)
This thread seemed promising but I could not get it to work. It is talking about Win8 but I thought I might be able to apply them to my situation.
I found a suggestion changing the BuildProvider assembly to type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.WEBFORMS ..." (instead of Common), but so far that is not working either.
Tried installing Report Viewer 11, and installing a very old version of our application. Both give me the same result.
Aha! OK, so it turns out that my issue is NOT with ReportViewer, but rather with RSClientPrint. Once I did a google search for that I quickly found that the answer is: Upgrade to Sql Server 2008 R2 SERVICE PACK 2.
The version of RsClientPrint you get with R2/SP2 is 10.50.4000, while the version I had was 10.50.1600.
In conclusion, it appears that RSClientPrint 10.50.1600 is NOT COMPATIBLE with IE10, but version 10.50.4000 IS.
I REALLY hope this helps someone else!!
I'm getting crazy with this problem. I got in my hands a Windows XP embedded and I need to install Framework .NET3.0 and I tried everything in my mind. I've been reading a lot of wXPe and everybody says that you have to take the XPe Rollout 1.0 from your tools and remake the image.
This is my biggest problem, I didn't have any of this tools, I just have a computer with wXPe installed and I need to install my software and I don't have any kind of feedback of who have done it.
I spend a lot of time to understand the ewf and finally I get disabled. But now, I need .NET3.0 and once I get unpacked I can continue with the installation, it seems freezed, I can't continue with the installation.
I've tried to install .NET2.0, it unpacks but suddently stops.
Any idea?! I'm start thinking that is impossible without rebulding the image, but at this time, this is not an option.
Thanks!
Did you manage to get .Net framework installed on your XP Embedded image?
The problem with XP embedded is, if you leave one component out while building your image then some features/programs won't work or install.
I had the same problem with one of my XP embedded images and I figured out that I had to add the .Net framework 2 component in order to install .Net framework 3 on the image. A website I find handy is this one, there's sld's on the website you can use, if you don't have the platform builder, I will be able to help you to build a new image