Why is the Framework VB.net 4.0 application (standard EXE) trying to write to the ASP.net registry key in HKLM?

I wrote a framework.net 4.0 application (on VB.net). This is a simple thing, basically just a screensaver with a few bells and whistles.

However, the webclient.net functions are used to query various sites on the Internet.

But this is NOT a web application. It does not run under ASP or, as far as I can tell, it has NOTHING to do with ASP.net.

However, when I run it on a computer with Comodo Firewall installed, I get warning pop-ups from Comodo indicating that

1) the program is trying to access the Internet (this is good, there are no problems).

but

2) That the program is trying to create registry keys, such as: HKLM \ System \ ControlSet001 \ services \ asp.net_4.0.30319 \ names {somelonghexvalue}

Now I have always followed the rule that basically the only things that are extinguished in HKLM are the installers, but here this application is trying to do something. And it comes from the .NET Framework, my application does not request any keys from the registry.

I assume that this is what was provided to the platform, even if the current user does not have rights to create keys in HKLM (since I do not get any errors, even if the application runs under credentials with very few rights).

So, to my question, has anyone come across this before or had any idea of ​​why the infrastructure will create ASP.Net registry keys when starting a standard EXE that has nothing to do with ASP.net?

I raised this question, Changes in the ASP.NET 4 registry, but the crawler in this case actually dealt with ASP.net applications. In this case, I do not know.

- EDIT-- Added code used to execute HTTP Get for Clara

Dim request As HttpWebRequest = DirectCast(WebRequest.Create(requestUri), HttpWebRequest) Dim resultPage As String = String.Empty Using httpWebResponse As HttpWebResponse = DirectCast(request.GetResponse(), HttpWebResponse) Using responseStream As Stream = httpWebResponse.GetResponseStream() Using reader As New StreamReader(responseStream) resultPage = reader.ReadToEnd() End Using End Using End Using 
+4
source share
1 answer

For some reason, it is updating ASP.NET performance counters, although I'm not sure why.

This registry key stores the named pipe name for ASP.NET:

The names of the pipes. One for each running workflow. See "What happens in runtime?" This subkey is displayed only on 32-bit versions of keys.

...

At run time, when the web application starts and the workflow starts, it loads webengine.dll (or webengine4.dll into .Net 4.0). This library, among other things, initializes the local performance store in this process. It will also create a named pipe to which clients can connect and read data counters. The name of the pipe is stored in HKLM \ SYSTEM \ CurrentControlSet \ Services \ ASP.NET_x.x.xxxxx \ Names is the registry key, so customers can find it.

Named pipe processing is asynchronous. The library uses the CLR IO, which wakes up every time

References:

ASP.NET Inside Elements - Performance Counter Performance Information

+1
source

Source: https://habr.com/ru/post/1410921/


All Articles