Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding custom file extensions to be opened with AsmDude #8

Closed
Tinister opened this issue Apr 8, 2016 · 1 comment
Closed

Adding custom file extensions to be opened with AsmDude #8

Tinister opened this issue Apr 8, 2016 · 1 comment

Comments

@Tinister
Copy link

Tinister commented Apr 8, 2016

It would be really nice to allow custom file extensions (e.g. "*.iasm") to be opened with AsmDude.

The Visual Studio Way of doing that usually is going to Tools -> Options -> Text Editor -> File Extension, then typing in the extension and which editor to open it with. However, I have no clue how much effort it is to make Visual Studio recognize AsmDude as an "editor".

@HJLebbink
Copy link
Owner

Yes that would indeed be a nice feature.

It is very easy to add a file extension in the source code, but sadly it is very difficult to do this such that it can be configured in e.g. Tools>Options>AsmDude. I guess it is possible, but I'm not aware of a method to achieve this. If you know how to do this, please let me know.

You could clone the repository, add the following lines, compile the .vsix, and install it. You need not wait for a next release.

If you insert:

[Export]
[FileExtension(".iasm")]
[ContentType(AsmDudePackage.AsmDudeContentType)]
internal static FileExtensionToContentTypeDefinition AsmFileType_iasm = null;

at line 94 in AsmClassifier, you would be done.

If you think this a common extension for assembly files, I could add it for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants