IIS Express w/ VS 2022 crashes when debugging web app and selecting file via file html input on page w/ ExtJs

By -

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



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more