View previous topic :: View next topic |
Author |
Message |
ctlajoie
Joined: 17 Nov 2005 Posts: 15
|
Posted: Sun Jan 15, 2006 2:18 pm Post subject: Bugs |
|
|
We need some people to test it out and report any bug you come across (even if it seems so obvious there's no way we could miss it )
one obvious bug I am working on fixing now (jan 15, 2006): dmd compiler path is hard-coded. I need to do some research to find out if there is any convention on where this path is stored in the registry. Once done, the installer will ask the user to specify the location of their dmd compiler.
My hope is we can make this thread function as our todo list. |
|
Back to top |
|
|
larsivi Site Admin
Joined: 27 Mar 2004 Posts: 453 Location: Trondheim, Norway
|
Posted: Sun Jan 15, 2006 6:31 pm Post subject: Re: Bugs |
|
|
ctlajoie wrote: |
one obvious bug I am working on fixing now (jan 15, 2006): dmd compiler path is hard-coded. I need to do some research to find out if there is any convention on where this path is stored in the registry. Once done, the installer will ask the user to specify the location of their dmd compiler.
|
The path to dmd isn't in the registry, Couldn't you just search $PATH for dmd? |
|
Back to top |
|
|
ctlajoie
Joined: 17 Nov 2005 Posts: 15
|
Posted: Mon Jan 16, 2006 12:01 am Post subject: |
|
|
ok, yeah that makes sense. I will search the PATH and if it is found I will set a registry value for quick retrieval next time. The registry value I believe is the standard way compiler paths are determined in VS. That goes for pretty much everything else in VS as well.
Chris |
|
Back to top |
|
|
larsivi Site Admin
Joined: 27 Mar 2004 Posts: 453 Location: Trondheim, Norway
|
Posted: Mon Jan 16, 2006 12:16 am Post subject: |
|
|
ctlajoie wrote: | ok, yeah that makes sense. I will search the PATH and if it is found I will set a registry value for quick retrieval next time. The registry value I believe is the standard way compiler paths are determined in VS. That goes for pretty much everything else in VS as well.
Chris |
I thought even MS was moving away from the registry, and over to xml-based config files? Not that I care |
|
Back to top |
|
|
ctlajoie
Joined: 17 Nov 2005 Posts: 15
|
Posted: Mon Jan 16, 2006 10:45 am Post subject: |
|
|
larsivi wrote: | I thought even MS was moving away from the registry, and over to xml-based config files? Not that I care |
I read that too. A lot of the tools in the .net runtime actually do use .config (xml) files, which is not the typical MS style (no theories on why). I believe the primary reason for the config files was to make configuring web apps easier, because it can be done from ftp .
All of their big apps still rely heavily on the registry, and COM can't exist without it. Also, I heard vista is going to feature a redesign of the registry. This leads me to believe that they are not "phasing it out" or even that they are favoring xml config files. I guess it's possible the .net programmers at MS just prefer config files more often than not.
just as a small note, I preferred to use ini (or more recently, xml) files for the longest time (and still do in some cases). But there's something oddly appealing (to me) about a common location to store all application preferences.
Chris |
|
Back to top |
|
|
rsl
Joined: 04 Jan 2006 Posts: 47
|
Posted: Mon Jan 16, 2006 6:28 pm Post subject: |
|
|
Compiler settings should be there at "[Tool][Options][Projects]" page.
needed properties are.
-dmd compiler path settings
-import path settings its passed to dmd with -I option.
and this settings should be stored at registry. to support automation and Import/Export settings.
see "ToolOptions" sample to do that. this sample create ToolOptionPage.
and write settings to registry. |
|
Back to top |
|
|
ctlajoie
Joined: 17 Nov 2005 Posts: 15
|
Posted: Mon Jan 16, 2006 9:42 pm Post subject: |
|
|
I posted an update to class1.cs in the DMD MSBuild extension project. It searches for the compiler path in HKCU/Software/VSPluginD/CompilerPath. If that registry key doesn't exist, it searches the PATH. go ahead and try it out. I think this is the most important bug right now because it's preventing people from even compiling the default project, so maybe we could get a new installer up soon.
If I have time tomorrow I will work on the things you mentioned.
Also can you email me the Installer project? Thanks!
Chris |
|
Back to top |
|
|
rsl
Joined: 04 Jan 2006 Posts: 47
|
Posted: Mon Jan 16, 2006 11:08 pm Post subject: |
|
|
I've tested searching path feature, and working well.
I've added error handler, case dmd.exe is not found.
sorry for forgetting to add log comment to svn. Is is able to add that ,after src comitted?
and new installer, I think, it is better to wait until we can add tool options page.
I test "ToolOptions" page sample. and it seems that automatically write info to registry to [HKEY_CURRENT_USER].....[8.0Exp][DialogPage].
and I can't found a way to change that place.
I upload what I changed to "DProject" to svn until tomorrow. |
|
Back to top |
|
|
rsl
Joined: 04 Jan 2006 Posts: 47
|
Posted: Tue Jan 17, 2006 4:46 am Post subject: |
|
|
I've added ToolOptionPages support.
all settings are stored at "HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0Exp\VSpluginD\"
two value are created after open ToolOptionPage.
-CompilerPath
-ImportPathList
these keys should be created by install time also.
TODO:
-ImportPathList is ';' separated path list. Is there registry string value length limitation?
-ToolOptionPage Control: Add button that change order of importList. |
|
Back to top |
|
|
ctlajoie
Joined: 17 Nov 2005 Posts: 15
|
Posted: Tue Jan 17, 2006 9:59 am Post subject: |
|
|
rsl wrote: | I've tested searching path feature, and working well.
I've added error handler, case dmd.exe is not found.
sorry for forgetting to add log comment to svn. Is is able to add that ,after src comitted?
|
I don't know if there is a way to change the comment. I am sure there is. It doesn't matter, I can just do a diff if I really need to know. The comment is just a time-saver.
rsl wrote: | I test "ToolOptions" page sample. and it seems that automatically write info to registry to [HKEY_CURRENT_USER].....[8.0Exp][DialogPage].
and I can't found a way to change that place.
|
No need. I will change the path I used (HKCU/Software/VSPluginD) to the correct location that you mentioned. |
|
Back to top |
|
|
ctlajoie
Joined: 17 Nov 2005 Posts: 15
|
Posted: Tue Jan 17, 2006 10:28 am Post subject: |
|
|
rsl wrote: | I've added ToolOptionPages support.
all settings are stored at "HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0Exp\VSpluginD\"
two value are created after open ToolOptionPage.
-CompilerPath
-ImportPathList
these keys should be created by install time also.
TODO:
-ImportPathList is ';' separated path list. Is there registry string value length limitation?
-ToolOptionPage Control: Add button that change order of importList. |
Not sure if there is a limit on the lenght of a string value in registry, but if there is it is very long. I have seen it used (foolishly) to store html pages before.
edit:
I think in addition to the ImportPathList on the ToolOptionsPage we need to have specific import paths on the project level. Meaning we need to store a list of import directories in the dproj file as well.
I am very busy today so I will not have time to do anything until tomorrow.
Chris |
|
Back to top |
|
|
drkIIRaziel
Joined: 21 Jan 2006 Posts: 15 Location: Athens,GR
|
Posted: Mon Jan 23, 2006 8:46 am Post subject: |
|
|
"this" keyword not colored .
error lines seem to be wrong here (allways points to next line). |
|
Back to top |
|
|
rsl
Joined: 04 Jan 2006 Posts: 47
|
Posted: Mon Jan 23, 2006 9:43 am Post subject: |
|
|
Fix these bugs. Thanks for reporting that. |
|
Back to top |
|
|
drkIIRaziel
Joined: 21 Jan 2006 Posts: 15 Location: Athens,GR
|
Posted: Mon Jan 23, 2006 9:47 am Post subject: |
|
|
If link fails and then you repress build , build won't be done cause vs things
that build was sucessfull.Also rebuild does not work at all here
If i add a new folder on the project , then add source files to it and the previus build failed on link the vs won't do a build cause it things that its not needed (!!!) . May hapen also without the link failure , haven't tested.. |
|
Back to top |
|
|
rsl
Joined: 04 Jan 2006 Posts: 47
|
Posted: Mon Jan 23, 2006 12:54 pm Post subject: |
|
|
Rebuild and Clean operation is not implemented,.
If you need to rebuild, edit source then build.
and I confirm when LinkerError occuered, then next build operation return "project updated". It's bug to be fixed. |
|
Back to top |
|
|
|