In case you need to work with old code that was not updated.
2019 version: https://code.visualstudio.com/updates/v1_33
Bruce Ng's software development blog
An archive of solutions of programming problems I have faced in my career
In case you need to work with old code that was not updated.
2019 version: https://code.visualstudio.com/updates/v1_33
If this happens, launch the setup program again (maybe go to Control Panel -> Programs and Features -> Uninstall). Then choose Repair, browse and select the folder of the SQL Server setup files.
After reparing, run the installer again, installation will be successful.
When trying to debug an Ionic Angular application in an older version of Visual Studio Code, this error shows up.
Follow the checklist
The best way is to update your code base to newer versions of languages, frameworks and libraries so you can use newer tools to debug the application. Otherwise this is a workaround.
When not sure the root cause, try disabling Http2 protocol in the web server, either IIS or Apache.
In the web UI of VMware, click console, then choose “Download VMware remote console”. You may have to sign up for a VMWare account to download.
This is a native remote client, the web remote console sometimes has issues with mouse integration with different guest OSes.
Go to root node of IIS -> Authentication -> Anonymous Authentication, check which user the anonymous inherits the permissions from, set it to ApplicationPoolIdentity.
Then make sure the ApplicationPoolIdentity has permission to access the folder.
Source: https://stackoverflow.com/questions/28939022/get-raw-query-from-nest-client/50023531#50023531
For NEST / Elasticsearch.NET v6.0.2, use the ApiCall property of the IResponse object. You can write a handy extension method like this:
public static string ToJson(this IResponse response)
{
return Encoding.UTF8.GetString(response.ApiCall.RequestBodyInBytes);
}
Or, if you want to log all requests made to Elastic, you can intercept responses with the connection object:
var node = new Uri("https://localhost:9200");
var pool = new SingleNodeConnectionPool(node);
var connectionSettings = new ConnectionSettings(pool, new HttpConnection());
connectionSettings.OnRequestCompleted(call =>
{
Debug.Write(Encoding.UTF8.GetString(call.RequestBodyInBytes));
});
You need to call on the ES client connection setting object to allow reading request JSON. This is best done on DEBUG mode.
connectionSettings.DisableDirectStreaming(true)
All bool queries are evaluated on a single document.
So if you have an index like this
Products= {
Fields: { Name: string; Value: int; }[];
}
And you want to find products with field “Price” between 10 and 20, and field “Discount” between 0 and 5, you can use the following query
bool: {
must: [
{nested: { //nested query to find products with price from 10 to 20},
{nested: { //nested query to find products with Discount from 0 to 5}
]
}
It looks quite hard to follow.
A quick workaround is to set NLA off under “Allow remote access to this computer”. Just uncheck the option that mentions NLA.
This is not recommended for production environment, just for development and testing.
If you face this errors when running some ASP.NET applications, it is because of assembly redirection.
At the moment I’m not sure how it works, but if there are some assembly redirection written in your web.config file, comment them out and it may solve the problem.