Why am i getting this error trying to compile an asp.net-mvc app using Parallels on my MacBook - asp.net-mvc

I posted a question on the apple site but someone suggested that I might get a better response on stackoverflow directly since its a visual studio related issue.
I installed parallels on my macbook pro and i installed windows 7 iso via a DVD. at first everything looked fine exception now I am now trying to compile an asp.net-mvc app in visual studio and i get this error over and over
No matter what i click it will eventually progress but this is quite annoying. The same question was asked here but no good answer was given. It almost seems like it think it needs to depend on something from the DVD drive (which it shouldn't)
Can someone please explain why devenv.exe would need the ISO dvd to be connected to my laptop at this point?

after rebooting this problem seems to go away

Related

Visual Studio 2019 editor fails to select modules in the editor

I have a problem with VS 2019 editor for a while, but it became a real problem lately.
Specifically, with the editor open, I cannot navigate to objects / classes and their methods or properties
You can see example in the screencast below.
https://www.screencast.com/t/0ceZ4C3TabY
I have the latest version, 16.10.2
This happens on two different PC's.
The problem started in a previous update, but I don't know which. I noticed it few times ago, but I didn't paid attention.
Does anyone else encountered it, and knows any solution?
Thank you
The problem was finally fixed in 16.10.3

Visual Studio for Mac won't update - Xamarin

Weird issue here. I have Visual Studio for Mac. My mac is fully upto date on the mac sidel. I have updated to Xcode 12.5. I have selected the check for updates option in VSMac. I see that there are a bunch of updates for xamarin on my mac. I selected for it to update and restart, and then nothing happens. VSMac just closes. I'm assuming I have something on my system that VSMac doesn't like. Is there a way to just get the downloads and manually install them?
Here was the way that I solved the problem. I went and downloaded the various pieces that I knew I had specific problems with. This was VSMac, Xamarin.iOS, and Xamarin.Mac. I downloaded those, and then installed the iOS and Mac versions. Everything was still good. Then I installed the most up to date VSMac. It detected the old versions of Mono, Android, and some other stuff, and downloaded and installed them. Now, my current problem is solved. There may still be others, but this got my immediate problem resolved.
Hopefully, this helps someone else in the future.

DirectX Sample using DXUT Failed to create Direct3D device (Debug only)

Quite a strange problem I have here, I am trying to run the DXUT DirectX 10/11 tutorials from DirectX sample browser. They build fine, but cannot be run in Debug mode, as this triggers the error warning "Failed to create the Direct3D device". This is strange as I can run them in release mode. The strangest thing however is that they use to run in Debug mode, and I swear I changed nothing in the day it ran, and the next day that it didn't. A friend also has the same exact problem, which happened around the same time.
Has anyone ran into this problem and know of a solution, or perhaps know why its happening beyond the obvious, I have a DirectX 11 capable card if you didn't pick that up.
Thanks.
I literally just spent all day trying to fix this exact same problem. Here is the solution which should hopefully fix yours too...
I managed to find this article explaining that a recent update, (26th February 2013 to be exact), caused the older version to mess up:
http://blogs.msdn.com/b/chuckw/archive/2013/02/26/directx-11-1-and-windows-7-update.aspx
That explains why it was working fine a few weeks ago, and now it just suddenly stopped working I guess!
Following their advice, I downloaded a trial version of Visual Studio 2012, and after an hour and a half of installation time, and a system restart, you should have all the new DirectX SDK files that you need.
NOTE: You don't even have to use Visual Studio 2012. The new files should fix your issues for Visual Studio 2010 and older versions I presume!
(Before doing this I also installed all the latest drivers, but I don't think that did anything to help, but it's worth upgrading drivers whenever you can, as that has fixed a similar issue I had before).
Hope this helps!!! :)
Somewhere in your code you probably have something along the line of this
#if defined(DEBUG) || defined(_DEBUG)
createDeviceFlags |= D3D10_CREATE_DEVICE_DEBUG;
#endif
If you do take a look at the D3D10_CREATE_DEVICE_DEBUG; on the msdn you will see this
To use this flag, you must have D3D11_1SDKLayers.dll installed;
otherwise, device creation fails.
You should check that you do have that dll in your system or you should reinstall the DirectX SDK.
The automatic IE10 update is what caused my issue of automatic non support of directx development. Simplest solution is downloading standalone win8 sdk at...
http://msdn.microsoft.com/en-us/windows/desktop/hh852363
The directx debug layer dll has to be updated.

Desperately trying to make Watin work with IE

I have been working with Watin for about 1 week. I really wanted to make firefox work but had to give up after a day or so when seeing there was no way i could get jSSH working with Firefox 8 etc. Really wish there was a way of using Chrome or firefox i have to say
So returning reluctantly to IE I developed some automation software using Watin, however I have a persistent problem with Goto(href) where it seems as though the page never actually gets marked as complete. And although the browser navigates to the page and I can see the page fine, the call to Goto() just times out. After that point anything I try fails and it cant find the elements in the dom and I cant click anything programmatically. So I have to solve this timeout issue
I have read various articles suggesting fixes and have tried them all as far as I can see i.e. making sure I run as administrator, making sure that internet explorer enhanced security is switched off, etc.. I would really, really like to make Watin work - but right now I am about ready to give up and create a much, much simpler class with an embedded browser in my app. So stackoverflow is my last port of call. How can I stop Watin from timing out.
I am on Windows 7 Ultimate Version 6.1.7601 Service pack 1 build 7601
Visual Studio 2010
compiling as a .net 4.0 app
IE 9.0.8112.16421 with update KB2586448
I have a console app, no threads, [STAThread] on my Main entry point
This is my Visual Studio info:-
Microsoft Visual Studio 2010 Version 10.0.40219.1 SP1Rel
Microsoft .NET Framework Version 4.0.30319 SP1Rel
Microsoft Visual C# 2010 01021-532-2002102-70185
Any help will be very greatfully received.
Regards Julian
ok, so after many months of playing and fiddling the answer to my question has several parts.
Firstly. I needed to get Watin working properly as an embedded browser in a win32 application rather than as a console app. This required me to spend a huge amount of effort getting Watin embedded the way I wanted, I had problems with STATHREAD (of course), and the pop up dialog watcher, and getting the HWND of my browser into Watin to create its browser object (I used another sample on stack overflow to do this) and then I had to ensure ScriptErrorsSuppressed=true and I finally got it working. Hoorah
However, the problem I originally had all that time ago still seems to remain with Watin.2.1.0.1196 in dealing with frame sets on asda.com.
So I have just now done a svn checkout of the watin project and I am finally hoping that the latest updates I have seen will fix this problem once and for all... and Yes I am still really looking forward to Jeroen getting IE9 or indeed any other browser working with Watin. Working with IE (any flavour) sucks
WaTiN does not support IE9 fully yet as far as I know. Jeroen (the creator) is working on getting it fully compatible with IE9, but IE9 relies on new WPF components in regards to previous versions of IE, so i'm guessing this will take some work.
We suffered from several problems as well when we upgraded our WatiN tests to IE9. In the end we force our website to render everything to IE8 standards and set IE9 to IE8 rendering mode untill there is an update from watin to fully support IE9 with all its quirkcs and features.

sourcelinks and fogbugz

I just installed this:
http://www.wholetomato.com/products/sourcelinks/FogBugzBundle.asp
but I don;t seem to be getting any of the functionality in my msdev. I am using 2008 professional.
Anyone have any experience with this tool? it does not seem to work for me at all. I never get the login dialog.
After about a week the Whole Tomato team gave me a solution that worked perfectly. Thanks for the support Mark, etc.
the answer is below
After doing some research, I came
across this page:
http://www.mztools.com/articles/2007/MZ2007009.aspx
that lists several possibilities why
it might not be showing up in the
add-in manager. One of them is:
"There is a reported problem that
happens when MSXML 6.0 is not
installed correctly. In this case the
Add-In Manager doesn't show any
XML-based add-in (using an .AddIn file
for registration). It shows only
registry-based add-ins. So, if the
Add-In Manager is empty when it should
show several installed add-ins (not
only yours), try reinstalling MSXML
6.0."
You might try reinstalling XSXML 6.0,
and see if that helps. Download link
is here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=993c0bcf-3bcf-4009-be21-27e85e1857b1&displaylang=en
I'd certainly try that before
reinstalling VS2008.

Resources