Re: Why does VS try to parse my .inc (assembler include files) as XML?
- From: "Mikhail Arkhipov (Microsoft)" <mikhaila@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 10 Oct 2005 21:39:23 -0700
On 10/10/05 17:24, in article u6REAofzFHA.1132@xxxxxxxxxxxxxxxxxxxx, "Ole
Nielsby" <ole.nielsby@xxxxxxxxxxxx> wrote:
> I'm migrating an assembly language project from NASM to MASM
> (yes I know they say assembly is dead but I have good reasons).
>
> I managed to convert the files to MASM syntax and assemble
> most of them. However, when the assembly fails because of
> trouble in the include files (*.inc), VS tries to parse them as
> XML and spews a shower of error messages when this fails.
>
> I'm not too familiar with VS - how do I tell VS that the .inc
> files should be treated as plain text and not XML?
>
> I tried to use *.ina instead of *.inc but the problem prevails.
>
> I'm using VS2005 beta 2. (Yes, I really need to combine
> assembly language with the .NET2 framework - and no,
> it's not for reverse engineering.)
>
> ON/Remove the slow slimy animal from my reply address
>
>
File | Open
Click little arrow on the Open button
Choose Open With...
Select 'Text Editor'
Click 'Set as Default'.
Thanks
Mikhail Arkhipov (Microsoft)
-- This post is provided 'AS IS' with no warranties and confers no rights
.
- References:
- Why does VS try to parse my .inc (assembler include files) as XML?
- From: Ole Nielsby
- Why does VS try to parse my .inc (assembler include files) as XML?
- Prev by Date: Re: Visual Web Developer Controls not listed at top of source page
- Next by Date: RE: "Installation User Interface Option"??????
- Previous by thread: Why does VS try to parse my .inc (assembler include files) as XML?
- Next by thread: RE: "Installation User Interface Option"??????
- Index(es):
Relevant Pages
|