L
Lucvdv
This has been reported as far back as March, but it looks like it still
hasn't been fixed.
When you right-click a .vbs script or a .vb file (Visual Studio .Net VB
source), go through "open with" and select an application to open it with,
MSAS pops up a confirmation dialog.
For example right-click a .VB file, select "Open with", and choose
notepad.exe.
In the dialog that pops up, click "allow".
The _default_ (Open) verb for the file will now be executed instead of the
application you selected.
In the case of .vb that means the file is opened in Visual Studio, but if
it is a .vbs file it is executed (instead of being opened in Notepad or
so), which may have unintended consequences.
This happens only the first time a file is accessed: if you repeat the same
action on the same file, MSAS will have remembered that you allowed it the
last time, and the choice you selected will be performed (as it should be)
instead of the default.
hasn't been fixed.
When you right-click a .vbs script or a .vb file (Visual Studio .Net VB
source), go through "open with" and select an application to open it with,
MSAS pops up a confirmation dialog.
For example right-click a .VB file, select "Open with", and choose
notepad.exe.
In the dialog that pops up, click "allow".
The _default_ (Open) verb for the file will now be executed instead of the
application you selected.
In the case of .vb that means the file is opened in Visual Studio, but if
it is a .vbs file it is executed (instead of being opened in Notepad or
so), which may have unintended consequences.
This happens only the first time a file is accessed: if you repeat the same
action on the same file, MSAS will have remembered that you allowed it the
last time, and the choice you selected will be performed (as it should be)
instead of the default.