I'm currently using VS11 beta in a VM but its far to slow and it has crashed. But I was also installed under windows 8 which i found slow so i'm not sure if the speed problems is related to windows8+running in VM or if the produce is also slower.
Is VS11 beta stable on windows7? Does it crash often? (it crashed multiple times for me under windows8 in a vm). Will i have problems developing .NET 2-3.5? Can i have a duel install with 2010 + 11beta?
What should i know before installing the beta on my main machine?
It appears to be very stable.
Personally, I've been using it on Windows 7 for quite a while now (from pre-beta) and have had zero crashes. I've also used it in Windows 8 and haven't seen any speed issues (both bootable VHD and a VirtualBox VM). Your experience may be different.
You can run VS2010 and VS11 side by side. If you have VS2010 SP1 installed projects can be round-tripped so that after you upgrade the project in VS11 it will still work in VS2010.
Working on .NET 2.0 and above is supported.
Related
i have developed an application (game) on visual studio 2012 (WFA) in C#, the application includes multithreading and graphics objects (pictureboxs, bit maps, labels...).
now the app runs great on the source pc (the computer it was developed on). but when i try to run it on my laptop it's run with very heavy flickering which is very weird.
source pc - windows 7 net framework 4.6 .
laptop - windows 10 net framework 4.6
*note - both are very strong machines who can run battlefield 4 with no problem.
what is going on??
You've got a software component issue - something that works correctly in 32 bit winDoze is broken in the 64 bit version. Try building your application as specifically 32 bit and run it on the 64 bit machine. Either it will complain about a missing (32 bit) driver (or other softwar component) or it will work correctly.
I have had webdeploy running for YEARS on a Windows Server 2012 machine with standard MSBuild arguments (like this).
Yesterday I installed the Windows (Server Hosting) version of the .NET Core Installer from the .NET Core downloads page.
Since then my build tasks are running and successfully building my website, but not actually running any web deploy publishing. It is not failing - it is just not being run.
I want to stress I am talking about a 'legacy' .NET application - not a .NET Core application. I just installed .NET Core for somebody else.
I can verify this with the following observations:
There are no errors in any event viewers (except ones that are months old)
There is no message in the msbuild logfile that says Start Web Deploy Publish, however log files from just a couple days ago do have this message.
I can connect to the local server at port 8172 and it makes a connection.
It is happening with multiple projects that nobody else has access to.
_PublishedWebsites does get created with the latest files - it just never gets deployed anywhere.
What could possibly have broken this? Did the Windows Server Hosting package break it - or was it just some other update that came in? I've run out of ideas how to fix it and don't want to revert to xcopy!
Managed to fix it :-) Not sure exactly which of these steps did it, but I suspect it was Visual studio.
I was using TFS Express 2015 and upgraded to Update 3.
I also installed Visual Studio 2015 on the server itself.
I had previously had .NET Core RC2 (or whatever they called it at the time) installed and I uninstalled that before installing .NET Core RTM. Wondering if that removed some component that was required.
Like I said everything was working fine before I installed the .NET Core RTM - but fortunately installing VS and TFS brought everything back to normal.
I recently migrated windows 8.1. But unable to open vs2013/vs2012 new Project template.
IT was working fine in windows 8.
ERROR: Failed to create imageSource from the text '..\Images\Medium.png'
Tried all options but did not succeed.
Please HELP
This is because you migrated from windows 8 to windows 8.1
First Go to Control Panel --> Check Updates for Windows 8.1
Install All Important Updates
Restart Your Pc
All things will properly work..
I tried almost every solution I found.
I would like to share, what I have tried and did not work and what did work and solved the problem.
Here are the "solutions" which did not work for me but claimed that they worked for some people.
1) Removing FastPictureViewer Codec Pack (which was already not installed)
2) Having a modify permission to everyone for
c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config
and
c:\windows\microsoft.net\framework\v4.0.30319\config\machine.config
3) Using Procmon to see broken registries
4) Uninstalling/reinstalling VS13 and all shared packages
5) Renaming the machine.config.default to machine.config
6) Running Visual Studio as an administrator
And this what it solved it:
Simply installed all the updates for windows 8.1 (not only the important ones, also optional updates as well) and restart. It sounds crazy after spending hours and hours but that solved my problem.
Good luck!
I tried all the steps mentioned above and it did not work. Even I was not able to uninstall VS.
I reapaired .NET framework through Contrl Panel->Programs and Features-> Microsoft .Net Framework-> right click Chane/Uninstall Repair .Net Framework.
This solved the problem.
I got same error after Oracle Data Provider for VS 2013 installation. I installed all Windows 8.1 Important Updates but it didn't work. I read somewhere that it can be happened because of lastly installed VS Add-On etc. then uninstalled Oracle Data Provider for VS 2013 and problem solved.
I am using Visual Studio 2012. This problem occurred to me after I upgraded from Windows 8 to Windows 8.1, so it is definitely related to the OS upgrade.
As some answers say, installing updates for Windows 8.1 will resolve the issue. But you don't need to install everything. I installed only the .NET related updates. Specifically, I installed "Microsoft .NET Framework 4.5.2 for Windows 8.1" (KB2934520), and a few others "Security and Quality Rollup" updates as well.
After a reboot, the "Loading Components" dialog shows up briefly upon launching Visual Studio, indicating that the cache of some components are invalidated and they are compiled again. After that, the "Add Reference" dialog works again.
My development machine is running Windows XP SP2 (and IIS 5.1 by implication).
Until recently our deployment environment was based around Windows Server 2003 (and therefore IIS 6.0).
We are about to move to Windows Server 2008 (and therefore IIS 7.0) for a new project.
Our projects use ASP.NET MVC and WCF Services.
Are there any key reasons for us to upgrade our development machines to run Windows Server 2008 (or possibly Vista, since this also comes with IIS 7.0)?
I would say it's in your best interest to upgrade your development machines to emulate as much of the production environment as possible within your means and resources. Otherwise you may fall into traps you're completely unaware of just by deploying an application from your development machine to the server's environment, which may pertain to differing versions of IIS, the version of .NET framework each machine is running, or just the way the code is compiled or executed at runtime.
Especially since IIS 7 has been vastly upgraded since IIS 5.1, why shouldn't you work closer with it's current functionality while developing before you missing out on some great opportunities? To really know what to expect from an application in production, develop it under the same circumstances.
Edit/Added: This link may help you see at least one significant example of how differing versions can affect your project.
I would recommend that you develop against the same major build as you intend to deploy on. That said, this leaves you with a few options. First, you could build against your local IIS installation (as it appears you currently do). That means that all of your boxes should likely be upgraded to Windows Vista or Windows 2008 Server (or Windows 7 as it is running IIS 7.5). Your second option is to deploy to a remote machine. It is entirely possible to deploy your application to a remote test machine running IIS 7 and remotely debug as well. The problem is that if you have more than one developer working on the remote site, it becomes problematic. IIS can handle the remote debugging on different webs for different developers, but depending on your architecture and configuration, you may still be sharing resources between instances of test web applications.You could occasionally deadlock each other. The only benefit is that you don't have to buy licenses for all of your machines (and potentially upgrade hardware to support the OS upgrade). However, I think that would be short-sighted. The loss of developer productivity wouldn't be worth it, IMHO.
There are major changes between IIS 5.1 and IIS 7.x. The changes to the architecture, such as the integrated pipeline, can result in drastically different behavior and compatibility issues. I think you will find that IIS 7 far more developer-friendly. The introduction of things such as failed request tracing, extended logging, and enhanced error pages alone make it much easier to track down errors in your application. In that regard, the upgrade is well worth it.
I have a situation where i need to debug a Windows CE application in both Vs.NET 2008 as well as VS.NET 2005.
After I switch between the emulators in these 2 environments a few times, i get the error:
A fatal error has occurred and debugging needs to be terminated. HRESULT=0x8013110e. Error code=0x0.
Why should it happen only after switching back and forth? The task manager shows sufficient memory and I am not able to debug this.
What could be the problem ?
Regards,
Chak
I'd wager that this has something to do with both development environments being installed at once. You can install multiple Visual Studio dated versions at once, but they have to be installed in date order. Perhaps the 2008 emulator package was conflicting with 2005?
There are a number of issues with these emulators if you have PAE installed on XP, certainly more than suggested in the linked MS tech note. Try disabling PAE and see if it cures your problem.
Thanks . We tried this. However, when we deploy the application on the VS.NET 2005 it does so, but when the same is done VS.NET 2008 app, it fails to load in the emulator. So there seems to be some corruption of shared resources.
If we uninstall 2005 and work only in 2008 it works.
Thanks,
Chak.
Maybe but we just put the two installations on two different boxes, before i read your mail. Maybe that was it.
Thanks.