Windows 7: File type Association (.exe, .jpg, ...) Add extension?

.
javascript .js files are associtated with WordPad.exe. ...should be Notepad.exe

.js file extension is missing in the Default Programs-Associate file type....

How can I add and extension(.js) to the list of extensions and protocols?
.

It's in mine as

.js | JScript Script File | Microsoft Windows Based Script Host




Here. Try to import it or merge. Then change to your liking.

Hello NIQ, and welcome to Seven Forums.

In addition to Torrentg's post, the js download in the tutorial below should restore the default associations for it.

Default File Type Associations - Restore

Afterwards, you can right click on the .js file and click on Edit to open it on Notepad by default.

Hope this helps,
Shawn

Thank you both,

Somehow after restarting, the .js showed up.
...and now I know of 2 ways(above mentioned) to resolve the issue if it is to reoccur.
Thank you.

...one point I should make.

I ran into this seemingly problem due to a really wierd behavior in Visual Studio 2008, where a .js file when clicked to be edited would show a tab but never show the code itself.

I assumed since the file association was wrong, somehow the file had been saved in an incompatible text mode.

I have now found out that the problem only arises when more than one .js file is brought into edit in a Visual Studio 2008/WIN 7 scenario?
CORRECTION: Even if a new Web App Project is created and 1 folder(includes) with one blank .js is added, it fails to show code and the environement start to misdraw the Solution Explorer pane... if I EXCLUDE the .js from the project... and (re) include it, I sometimes can get it to come up... anyhow the behavior is totally inconsistent.

Do you know of a forum like this one where I can bring up this issue?
. t.y.

You're welcome NIQ.

I suppose that you could report this at the Microsoft Visual Studio 2008 forum pages.

yes I am going to take the steps to report it...
my previous version of VS did not have this problem.

I will reinstall and run all possible updates first...
...have added a CORRECTION in above post...
t.y.

.
as of 11-05-2009, this issue is resolved.

Reinstalling VS2008 and the SP1 Service pack separately,
cleared what I believe were intellisense issues,
that were due to a mismatch in software updates.
.

NIQ,

I"m happy to hear that you got it sorted. Thank you for posting back with your results.