Here are the details:
OS: Windows 2016 server accessed over RD
Dev tools: VS 2022 17.1.6 & VS 2019 16.11.11. I run VS in Admin mode (both)
IIS Express version: 10.0.22489.1000, 64 bit
Browser Chrome: 100.0.4896.127 (Official Build) (64-bit)
App:.net 4 webforms application that uses ExtJs 6.6.0 classic as front end
Antivirus: CrowdStrike, version 6.36.15005.0.
I have a form with a file field. This link has more information on how the upload works, it basically uses an iframe under the hood.
Now, in VS 2019 the upload works. In VS 2022 the upload doesn't work anymore and it returns the error: "Blocked a frame with origin "http://localhost:38991" from accessing a cross-origin frame." (the error is returned in the client JavaScript code). Just to be clear, I open exactly the same project in VS 2019 and it works, then I open the project in VS 2022 and the uploads don't work anymore.
Both use the same IIS Express process (64 bit). And one minor detail, the upload operation when run from VS 2022 kills IIS Express, it basically evaporates.
Any idea on how to fix this in VS 2022? For now, I have to use VS 2019 in order to be able to test uploads.
Thanks in advance.
Update:
I installed VS 2022 version 17.1.6.
Initially I thought IIS express evaporates upon uploading the file. It actually exits when I select the file in the Open dialog.
The program '[19000] iisexpress.exe' has exited with code 4294967295 (0xffffffff).
When I run the project without debugging, it works fine!
I changed the title of the post from:
ExtJs file upload getting: "Blocked a frame with origin "http://localhost:38991" from accessing a cross-origin frame." when run w/ VS 2022 IIS Express
to
IIS Express w/ VS 2022 crashes when debugging web app and selecting file via file html input on page w/ ExtJs
ok, found the answer here: IIS Express stops suddenly when I click on a text box in my web app.
This did the trick:
The checkbox was clear in VS 2019, a colleague confirmed the uploads work in VS 2019 even with the checkbox selected.
Related
I am debugging an ASP.NET MVC app from Visual Studio 2013. When I start the debug process from Visual Studio, IIS Express where app is hosted gets stuck (my app is not started). It often happens to me. In this situation, I manually stop IIS Express from the tray icon. Even stopping IIS Express from the tray icon I often need to stop manually the debugging from Visual Studio through the stop button. Once debugging is stopped, If I try to debug again it does not work, well, sometimes works and sometimes not, it is random. I have verified that if I clear all browser history and cookies, it works in most cases except for some time. Also I have observed that Visual Studio 2013 takes a long time to boot IIS Express where my ASP.NET MVC app is hosted. Finally, I have observed that my ASP.NET MVC app hosted in IIS Express sometimes is not being displayed correctly when debugging from Visual Studio, I mean, it is displayed without css styles being applied, it seems like css styles are missed. In this case, if I stop debugging and start it again it works.
So How can I improve or solve these kind of weird issues?
IIS Express gets stuck and css styles sometimes not being applied when
debugging an ASP.NET MVC application from Visual Studio 2013
This is a quite strange issue and l suggest you could try these suggestions
Suggestion
1) delete all caches under C:\Users\Administrator\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache, C:\Users\Administrator\AppData\Local\Temp and C:\Users\Administrator\AppData\Local\Microsoft\WebsiteCache.
2) close VS Instance, delete .vs hidden folder,bin,obj folder under the physcial path of the solution and then reopen your project
3) If you have IntelliTrace, please disable Enable IntelliTrace under Tools-->Options-->IntelliTrace-->General.
4) try another port like 56000 by right-clicking on the project-->Properties-->Web--> project url.
5) disable any third party extensions by Tools-->Extensions and Updates or just use devenv /safemode in developer command prompt for vs2013.
6) try to reinstall IIS on the control panel and if your IIS is not 10.0, I suggest you could download and use it.
In addition, VS2013 is too old and Microsoft does not continue to maintain it. So l suggest you could download and use the latest VS2019. It has more optimization and stronger performance than the previous VS and fixes some remaining issues from previous releases.
I have installed Visual Studio 2019 to do some testing on our code base ready for migrating from Visual Studio 2017, I am also testing to ensure it plays nicely with our TFS system (currently TFS 2018 on premises).
It looks as though the Visual Studio Work Item Form is back! (VS 2017 dropped support for this in favour of opening Work Items in a web browser). I've not managed to find any information on this. I like the fact that we might have the option to work with Work Items in the VS IDE as well as the web browser, however its return introduces a few issues:
We use a custom MultiValue control that does have support for the VS 2019 Team Explorer (it last worked in VS 2015). Do you know where I can get hold of a MultiValue control that will work on the Work Item form in the VS 2019 Team Explorer?
Given that the MultiValue control isn't working I would like to continue working with Work Items in a browser. The VS 2019 Team Explorer seems to favour opening Work Items within the IDE, how can I open them in a browser from within the VS 2019 Team Explorer? Better still, how can I configure it to open in a browser by default?
Is there a better place for me to ask these questions?
Work Items should default to opening in the web in Visual Studio 2019. That behavior has not changed from Visual Studio 2017.
There is an option under "Tools->Options->Work Items" to enable the "Legacy experience (compatibility mode)". It sounds like that option has somehow gotten enabled in your installation. If you switch that back to "Default experience", work items should open in the web.
Hope this helps.
Sorry for the inconvenience. This is a designed behavior right now.
Please take a look at this similar issue: TFS work items opened inside Visual Study no longer open in the web browser, they always open in the Visual Studio editor
According to the response from MSFT:
We have re-design the default landing page for work items in Visual
Studio 2019 which only works with server >= 2019. If server is <
2019, work items will be open in Visual Studio only.
Since you are using TFS 2018 with VS2019, you may have to open work item in web portal from browser directly right now. Otherwise, you have to upgrade your TFS version from 2018 to Azure DevOps 2019, if you insist on opening the work item in Visual Studio.
I cannot see the story board in Visual Studio 2013, when I open it it tells me
There was a problem rendering this document.
Also in the errors list I have the following:
The clocks on the Build Host and this Machine are out of Sync. Please make sure they are within 3 minutes (UTC) of each other.
Failed to retrieve SDK status from server Xamarin.iOS Extension.
Also the output from the MAC server log tells me:
Error sending iOS designer payload
What can be wrong here?
I was also having a similar problem where I couldn't open the story board in Visual Studio 2012 or 2013 (I didn't have any errors in my error list, just the error when displaying the designer). My setup is dev work in Windows 7 with Visual Studio 2012/2013 with a Mac acting as a Build Host. I had just updated my Xamarin version from 3.0.54 to version 3.3.47 (it had been a little while) and I had created a little prototype app a couple days ago with no problems, so I figured I had killed something with the update.
In my case, the solution was checking for updates in Xamarin Studio on the Mac, where it found several that needed updated. After installing the updates on the Mac side, I was able to display my story board in both Visual Studio 2012/2013 without issues... so I chalked it up to version mismatch issues between the Build Host and my dev environment in Windows.
I am using Visual Studio 2012 to develop an MVC 4 web application. I have also created a virtual directory on my local IIS 7 server which points to my MVC application. Both IIS and Visual Studio 2012 point to the same source code.
I usually edit JavaScript files and hit refresh on my browser to reload the JavaScript file.
For some reason whenever I edit the JavaScript via Visual Studio 2012 it is write protected (by IIS) so I have to touch the web.config file in order for IIS to release the file in order to overwrite the file. This is really annoying when debugging because I have to reload the application every time I make a minor change to a JavaScript file.
Has anyone had this issue and how did you resolve it.
Any help would be greatly appreciated. Thank You
After upgrading to VS 2012 any changes I make in my javascript classes do not seem to take effect until after I flush the browsers cache and rerun. i.e. Make change to line of javascript, run the website by click f5, changes are not there.
This wasnt occurring previously in VS 2010, or even the VS 2012 RC. Would there be a setting that is caching this?
Thanks