Dave,

I've got the same issues as everyone else.  That is: correct registry, but no colour.  I've just downloaded the VSID kit.

I'll let you know if its makes a difference.

Scott Egan

(I notice that being a day ahead here is Oz doesn't help me keep ahead of the posts; or doesn't anyone else work? ;)

I dont know if this helps:

ms-help://MS.VSCC.2003/MS.VSIP.2003/vsenvsdk/html/vslrfProjectConfigurationF orManagingDeployment.htm

I have VS.2003 and hope I can test it
Great Thanks !
"Dave Sieber" <dsieber@spamnot.sbcglobal.net> wrote in message
news:Xns94C8E2094EB97dsiebersbc@63.105.9.61...
> I have syntax highlighting for D working in Visual Studio .NET, but I
would
> like to have it tested on another machine before releasing it. I have all the MS dev tools and SDK's here on my machine, so no telling what might happen on a different machine.  This is pre-alpha, although it should do correct syntax highlighting. But I am really just interested in whether
you
> can load it or not.
>
> At this point it's a single DLL (43k .ZIP) which you can put anywhere and
> simply register with REGSVR32, then run VS.NET and D should be a new
> supported language in the editor (famous last words :-). I'm using VS.NET
> 2003, but I guess (hope) that it works on VS.NET 2002. I have no idea if
it
> would work on Visual Studio 6.0 or earlier, but I have a feeling it won't.
>
> The only caution I have is that apparently a bug in VS.NET causes any customizations you've done on the tool bar and keyboard assignments to be lost when installing a service like this, so if you've customized you
might
> want to back them up somehow. A tool like VSTweak can be used to import/export keyboard layouts, but I don't know about the tool bars.
>
> I guess I could email it to whoever wants to test it or even post it here. I don't want to put it on dsource.org or the wiki until I at least know it works and doesn't blow up your computer <g>.
>
> -- 
> dave

Works! as I now have the VSIP DLK - It would seem that eveyone who wishes to
test this is going to have to get the VSIP SDK.
According to:
ms-help://MS.VSCC.2003/MS.VSIP.2003/vsenvsdk/html/vsconOverviewOfVisualStudi
oSecurityVSPackageLoadKeys.htm

You can only get a package load key from MS.



"Scott Egan" <scotte@tpg.com.aux> wrote in message news:c5gdme$5dk$1@digitaldaemon.com...
> Dave,
>
> I've got the same issues as everyone else.  That is: correct registry, but no colour.  I've just downloaded the VSID kit.
>
> I'll let you know if its makes a difference.
>
> Scott Egan
>
> (I notice that being a day ahead here is Oz doesn't help me keep ahead of the posts; or doesn't anyone else work? ;)
>
>
>

"Phill" <phill@pacific.net.au> wrote:

> I seem to remember a couple of months ago,
> somebody suggesting that, seems MS have
> VB and VC++ that maybe "VD" would be a good name, I dont know if that
> would roll off the tongue
> though :o))

Yeah, you have a point :-)  Actually, I would like to take this beyond mere syntax coloring, and add support for Intellisense, and then beyond that add project support -- so "Visual D" is not a bad idea.  It did occur to me, though, that Microsoft may have some sort of protest against the use of that as a project name -- have they trademarked "Visual"?   Look what they did to wxWindows, and nobody was confused over that.

Well, it is still in pre-alpha testing, so I will come up with a decent name before the initial release.


-- 
dave

"Scott Egan" <scotte@tpg.com.aux> wrote:

> Works! as I now have the VSIP DLK - It would seem that eveyone who
> wishes to test this is going to have to get the VSIP SDK.
> According to:
> ms-help://MS.VSCC.2003/MS.VSIP.2003/vsenvsdk/html/vsconOverviewOfVisual
> Studi oSecurityVSPackageLoadKeys.htm
> 
> You can only get a package load key from MS.

This is good news, and glad to see it works.

I'm looking into the package load key situation. I believe if I get a key from MS, and embed it in the DLL, as the docs indicate, testers shouldn't have to install VSIP. I don't think anyone should have to do that just for using an add-in to Visual Studio -- but we're talking about lawyers and big corporations here, so common sense doesn't enter the picture :-)


-- 
dave

"Tu Nam" <dreamweaver@mail15.com> wrote:

> I have VS.2003 and hope I can test it

There will be another test version in a few days (hopefully) that gets around the product load key problem. I'll announce here when it's ready.

-- 
dave

Hey Dave

Could you provide us with a copy of the lex/grammars that you're using?

Also, how about opening the source and/or putting it on http://savannah.gnu.org/ ??

Cheers and good work,
Brian

In article <Xns94CA3E990548Cdsiebersbc@63.105.9.61>, Dave Sieber says...
>
>"Tu Nam" <dreamweaver@mail15.com> wrote:
>
>> I have VS.2003 and hope I can test it
>
>There will be another test version in a few days (hopefully) that gets around the product load key problem. I'll announce here when it's ready.
>
>-- 
>dave

Brian Smith <Brian_member@pathlink.com> wrote:

> Could you provide us with a copy of the lex/grammars that you're using?

Yes, I was planning on doing that. This first public test was just to see about problems loading it on other machines, because I suspected there would be some, and I didn't have a second machine here to test with. There are some problems with the code that I want to address before an official release -- it sometimes indicates syntax errors where there are none, for instance. I have only a lex spec at the moment, and support code for making that available to Visual Studio.

I am using Flex, but may end up using something else, if Flex doesn't have Unicode support (need to find out). Same for Bison -- without Unicode support, it doesn't fully support D.  And Walter has already been kind enough to provide us with his own lexing and parsing code, so I may graft that in instead of using a yacc-based grammar anyway. In fact, the only reason I started with Flex is as a feasibility study, because Microsoft's Babel SDK has a mode that supports Flex/Bison as a quick way of getting something up and running.

The thing is: with Babel, your Flex and Bison scripts have to be tweaked a bit in order to support syntax coloring and identifier lookup. They would probably not be suitable for general use with those tweaks. For instance, no token may be discarded (including white space), and at the end of a line you must always return a token (even inside multi-line comments and wysiwyg strings). My lex script does these things -- it returns *two* tokens for a string or comment on two lines, which is okay for on-screen coloring but not correct for real lexing. Also, you have to insert various actions in your bison script to provide scope and parameter information for Intellisense. These are optimizations for use as a programming aid within Visual Studio, not intended for general parsing.

Aside from all that, however, a publicly available grammar is a good idea, and there is interest in it, so I may try to do one anyway :-)

> Also, how about opening the source and/or putting it on http://savannah.gnu.org/ ??

I hadn't really thought about where/how I was going to release it, and it doesn't even have a name <g>, but dsource.org seems to be a good place. Like scratching an itch, I started it because I wanted it for my own use with D, but I figured others may be interested and I didn't see anything else out there. And language tools are a big personal interest for me.

-- 
dave

Dave Sieber wrote:

> Yeah, you have a point :-)  Actually, I would like to take this beyond mere syntax coloring, and add support for Intellisense, and then beyond that add project support -- so "Visual D" is not a bad idea.  It did occur to me, though, that Microsoft may have some sort of protest against the use of that as a project name -- have they trademarked "Visual"?   Look what they did to wxWindows, and nobody was confused over that.

I'd call it "Blind D", but I'm a gimp who once suggested naming an image library "Cataract". ;D

 -- andy