• Prudence (15/15) Sep 02 2015 I installed a completely new VS2015 and VD on a new Win10 setup.
• Rainer Schuetze (9/24) Sep 06 2015 I can confirm that there seems something weird. I also got this only
• Prudence (17/55) Sep 06 2015 Thanks, I didn't know that. (I ended up creating all the
• Rainer Schuetze (7/15) Sep 06 2015 That's what it's trying to do when it generates those additional '.' in
• Prudence (11/34) Sep 08 2015 hmm, ok. It seems to work most of the time. It might just be from

"Prudence" <Pursuit Happyness.All> writes:

I installed a completely new VS2015 and VD on a new Win10 setup.

I compiled a win10 app and it works. I proceeded to add a few 
empty D modules.

When I add a subfolder then add a d module to it, It first puts 
the name ".subfolder.dmodule". (note the . in front)

Also, even fixing the project won't compile and returns no error 
messages except failed. I've tried to delete the module and such 
and got it to compile again. Then tried adding once more and it 
didn't work. Trying to remove and close the d module then results 
in "insufficient memory to continue execution".

When I try to close Visual studio I get "The operation can't be 
completed. Not enough storage is available to complete this 
operation". Using latest of everything.

This seemed to only happen when I added a 3rd folder. Must be a 
bug in the software around that point.

Rainer Schuetze <r.sagitario gmx.de> writes:

On 03.09.2015 03:57, Prudence wrote:
 I installed a completely new VS2015 and VD on a new Win10 setup.

 I compiled a win10 app and it works. I proceeded to add a few empty D
 modules.

 When I add a subfolder then add a d module to it, It first puts the name
 ".subfolder.dmodule". (note the . in front)

I can confirm that there seems something weird. I also got this only 
after a few attempts.
Please note that "Add Folder" in the context menu is rather misnamed, it 
is actually the same functionality as "Add Filter" in C++, i.e. it 
doesn't create the directory on disk for you. That's done by selecting a 
package in "New item".

 Also, even fixing the project won't compile and returns no error
 messages except failed. I've tried to delete the module and such and got
 it to compile again. Then tried adding once more and it didn't work.
 Trying to remove and close the d module then results in "insufficient
 memory to continue execution".

I cannot reproduce this. Could you provide the output log 
(*.buildlog.html) in the output folder?


 When I try to close Visual studio I get "The operation can't be
 completed. Not enough storage is available to complete this operation".
 Using latest of everything.

 This seemed to only happen when I added a 3rd folder. Must be a bug in
 the software around that point.

"Prudence" <Pursuit Happyness.All> writes:

On Sunday, 6 September 2015 at 09:09:05 UTC, Rainer Schuetze 
wrote:
 On 03.09.2015 03:57, Prudence wrote:
 I installed a completely new VS2015 and VD on a new Win10 
 setup.

 I compiled a win10 app and it works. I proceeded to add a few 
 empty D
 modules.

 When I add a subfolder then add a d module to it, It first 
 puts the name
 ".subfolder.dmodule". (note the . in front)

 I can confirm that there seems something weird. I also got this 
 only after a few attempts.
 Please note that "Add Folder" in the context menu is rather 
 misnamed, it is actually the same functionality as "Add Filter" 
 in C++, i.e. it doesn't create the directory on disk for you. 
 That's done by selecting a package in "New item".

Thanks, I didn't know that. (I ended up creating all the 
directories manually ;/

I have a request related to this though.

When creating a module that is in a folder. VD does not use the 
folder name.

e.g., suppose you have the folder layout X\Y\Z

and add to it a file called q.d. When The file is open one has 
"module q;" instead of "module x.y.z.q;". The latter would be the 
preferred choice I suppose since I'm sure most people keep the 
module names consistent with their location(to avoid all kinds of 
problems). (this generally means if you are working on a large 
project there are many renamings that have to be done)

 Also, even fixing the project won't compile and returns no 
 error
 messages except failed. I've tried to delete the module and 
 such and got
 it to compile again. Then tried adding once more and it didn't 
 work.
 Trying to remove and close the d module then results in 
 "insufficient
 memory to continue execution".

 I cannot reproduce this. Could you provide the output log 
 (*.buildlog.html) in the output folder?


 When I try to close Visual studio I get "The operation can't be
 completed. Not enough storage is available to complete this 
 operation".
 Using latest of everything.

 This seemed to only happen when I added a 3rd folder. Must be 
 a bug in
 the software around that point.


Not sure. I can't reproduce it so I'm sure it was a glitch/bug 
but probably one of those things. If I run across it again I'll 
try to pay more attention.

Rainer Schuetze <r.sagitario gmx.de> writes:

On 06.09.2015 19:47, Prudence wrote:
 When creating a module that is in a folder. VD does not use the folder name.

 e.g., suppose you have the folder layout X\Y\Z

 and add to it a file called q.d. When The file is open one has "module
 q;" instead of "module x.y.z.q;". The latter would be the preferred
 choice I suppose since I'm sure most people keep the module names
 consistent with their location(to avoid all kinds of problems). (this
 generally means if you are working on a large project there are many
 renamings that have to be done)

That's what it's trying to do when it generates those additional '.' in 
"module .subfolder.dmodule;". Actually, Visual D tries to guess the 
package name from existing files in the same project folder, as well as 
looking in child and parent folders if its the first D file in the 
folder. It seems it doesn't do that if the package name in the root 
folder is empty.

"Prudence" <Pursuit Happyness.All> writes:

On Monday, 7 September 2015 at 06:42:40 UTC, Rainer Schuetze 
wrote:
 On 06.09.2015 19:47, Prudence wrote:
 When creating a module that is in a folder. VD does not use 
 the folder name.

 e.g., suppose you have the folder layout X\Y\Z

 and add to it a file called q.d. When The file is open one has 
 "module
 q;" instead of "module x.y.z.q;". The latter would be the 
 preferred
 choice I suppose since I'm sure most people keep the module 
 names
 consistent with their location(to avoid all kinds of 
 problems). (this
 generally means if you are working on a large project there 
 are many
 renamings that have to be done)

 That's what it's trying to do when it generates those 
 additional '.' in "module .subfolder.dmodule;". Actually, 
 Visual D tries to guess the package name from existing files in 
 the same project folder, as well as looking in child and parent 
 folders if its the first D file in the folder. It seems it 
 doesn't do that if the package name in the root folder is empty.

hmm, ok. It seems to work most of the time. It might just be from 
some buggy stuff that may or may not be part of VD. It's not a 
big deal either way. It might be due to the fact that creating a 
"new folder" doesn't actually create it, which I wasn't aware of. 
I'm creating the folders manually then importing them.

Another simple request. When renaming a module, could VD 
automatically rename the module name inside the file and/or 
reopen the file? (renaming causes the file to close and needs to 
manually be reopened)