On 05.02.2014 22:47, Rainer Schuetze wrote:
On 05.02.2014 13:21, Manu wrote:
Any chance you can release a beta with that settings bug fixed?
I've supervised 2 new VD installs the last couple of days, and they all
suffer the problem with the mspdb dll path not being remembered in the
exe pat
On 05.02.2014 14:20, Benjamin Thaut wrote:
Am 05.02.2014 13:21, schrieb Manu:
Any chance you can release a beta with that settings bug fixed?
I've supervised 2 new VD installs the last couple of days, and they all
suffer the problem with the mspdb dll path not being remembered in the
exe path
On 05.02.2014 13:21, Manu wrote:
Any chance you can release a beta with that settings bug fixed?
I've supervised 2 new VD installs the last couple of days, and they all
suffer the problem with the mspdb dll path not being remembered in the
exe path settings.
I didn't have a lot of time latel
Am 05.02.2014 13:21, schrieb Manu:
Any chance you can release a beta with that settings bug fixed?
I've supervised 2 new VD installs the last couple of days, and they all
suffer the problem with the mspdb dll path not being remembered in the
exe path settings.
Temporary workaround:
http://stuf
On 5 February 2014 16:55, Rainer Schuetze wrote:
>
>
> On 04.02.2014 18:47, ParticlePeter wrote:
>
>> On Wednesday, 13 November 2013 at 06:48:44 UTC, Rainer Schuetze wrote:
>>
>>>
>>>
>>> On 12.11.2013 10:19, evilrat wrote:
>>>
On Tuesday, 12 November 2013 at 08:06:24 UTC, Rainer Schuetze wr
On 04.02.2014 18:47, ParticlePeter wrote:
On Wednesday, 13 November 2013 at 06:48:44 UTC, Rainer Schuetze wrote:
On 12.11.2013 10:19, evilrat wrote:
On Tuesday, 12 November 2013 at 08:06:24 UTC, Rainer Schuetze wrote:
If you switch the debugger to "Mago", the conversion is no longer
needed
On Wednesday, 13 November 2013 at 06:48:44 UTC, Rainer Schuetze
wrote:
On 12.11.2013 10:19, evilrat wrote:
On Tuesday, 12 November 2013 at 08:06:24 UTC, Rainer Schuetze
wrote:
If you switch the debugger to "Mago", the conversion is no
longer
needed, so you can still build and debug Win32 exe
On 12.11.2013 10:19, evilrat wrote:
On Tuesday, 12 November 2013 at 08:06:24 UTC, Rainer Schuetze wrote:
If you switch the debugger to "Mago", the conversion is no longer
needed, so you can still build and debug Win32 executables.
mago gives "cannot launch debugger on %appname%. hr = 897..."
On Tuesday, 12 November 2013 at 08:06:24 UTC, Rainer Schuetze
wrote:
If you switch the debugger to "Mago", the conversion is no
longer needed, so you can still build and debug Win32
executables.
mago gives "cannot launch debugger on %appname%. hr = 897...", so
only x64 debugger left for usage
On 12.11.2013 08:25, evilrat wrote:
On Sunday, 10 November 2013 at 08:53:08 UTC, evilrat wrote:
ok i forgot about output pane. so what i see here...
ConsoleApp1\Debug\ConsoleApp1.pdb: cannot load PDB helper DLL
so the problem with debug server formats?
i wish it would work with visual studi
On 10.11.2013 08:13, Nicholas Londey wrote:
Have a look at this and see if that helps. I think I got it working in
vs2013 because it was the announcement that it should be working that
prompted me to find out why it wasn't.
http://d.puremagic.com/issues/show_bug.cgi?id=11457
Unfortunately th
Sorry for the delay, I've been away for a couple of days.
On 07.11.2013 07:13, Alexander Bothe wrote:
On Thursday, 7 November 2013 at 05:45:34 UTC, Rainer Schuetze wrote:
Yeah, being able to get releases out more often, and having bug fixes
being tested in the field would be nice. But I think
On Sunday, 10 November 2013 at 08:53:08 UTC, evilrat wrote:
ok i forgot about output pane. so what i see here...
ConsoleApp1\Debug\ConsoleApp1.pdb: cannot load PDB helper DLL
so the problem with debug server formats?
i wish it would work with visual studio 2013 soon, but at least
x64 debug wo
ok i forgot about output pane. so what i see here...
ConsoleApp1\Debug\ConsoleApp1.pdb: cannot load PDB helper DLL
On Sunday, 10 November 2013 at 07:13:26 UTC, Nicholas Londey
wrote:
Have a look at this and see if that helps. I think I got it
working in vs2013 because it was the announcement that it
should be working that prompted me to find out why it wasn't.
http://d.puremagic.com/issues/show_bug.cgi?id=
Have a look at this and see if that helps. I think I got it
working in vs2013 because it was the announcement that it should
be working that prompted me to find out why it wasn't.
http://d.puremagic.com/issues/show_bug.cgi?id=11457
On Saturday, 2 November 2013 at 14:40:56 UTC, Rainer Schuetze
wrote:
* Installer now supports VS 2013, updated to cv2pdb 0.27,
mago 0.8, fixes x64 debugger in VS 2012 Shell
unfortuantely it doesn't works with VS 2013, it installs and
registers with visual studio, but whenever i hit the b
On Thursday, 7 November 2013 at 05:45:34 UTC, Rainer Schuetze
wrote:
On 06.11.2013 09:25, Alexander Bothe wrote:
On Tuesday, 5 November 2013 at 05:09:58 UTC, Manu wrote:
Note: I saw Alexander Bothe released an update to the parser
one day
after
your release... ;)
Sure, there have been a co
On 06.11.2013 09:25, Alexander Bothe wrote:
On Tuesday, 5 November 2013 at 05:09:58 UTC, Manu wrote:
Note: I saw Alexander Bothe released an update to the parser one day
after
your release... ;)
Sure, there have been a couple of critical regression bugs in the parser
engine.
Furthermore, I r
On Wednesday, 6 November 2013 at 17:49:57 UTC, Dicebot wrote:
Picking common standard for all possible IDE's scales better
than cloning approach of a single one (especially if this one
is closed and known of forcing closed ecosystems)
Essentially, dub.
I'm okay with that decision :-P
Picking common standard for all possible IDE's scales better than
cloning approach of a single one (especially if this one is
closed and known of forcing closed ecosystems)
On 7 November 2013 02:05, Bruno Medeiros wrote:
> On 06/11/2013 14:39, Manu wrote:
>
>> For instance, it seems a shame to have .visualdproj, and .dproj files
>> separate and incompatible. .csproj files are the same between VS and MD,
>> I wonder if the same is possible for D with collaboration?
>>
On 06/11/2013 14:39, Manu wrote:
For instance, it seems a shame to have .visualdproj, and .dproj files
separate and incompatible. .csproj files are the same between VS and MD,
I wonder if the same is possible for D with collaboration?
The best approach here is to support an IDE-independent proj
On Wednesday, 6 November 2013 at 14:43:35 UTC, Dicebot wrote:
Regarding project files - I like Mono-D attempt to support dub
package.json as project description file.
Regarding semantical analysis - both Mono-D and VisualD should
just merged efforts with DCD, problem solved :)
I dunno, there
Regarding project files - I like Mono-D attempt to support dub
package.json as project description file.
Regarding semantical analysis - both Mono-D and VisualD should
just merged efforts with DCD, problem solved :)
On 6 November 2013 18:25, Alexander Bothe wrote:
> On Tuesday, 5 November 2013 at 05:09:58 UTC, Manu wrote:
>
>> Note: I saw Alexander Bothe released an update to the parser one day after
>> your release... ;)
>>
>
> Sure, there have been a couple of critical regression bugs in the parser
> engin
On Tuesday, 5 November 2013 at 05:09:58 UTC, Manu wrote:
Note: I saw Alexander Bothe released an update to the parser
one day after
your release... ;)
Sure, there have been a couple of critical regression bugs in the
parser engine.
Furthermore, I re-enabled the ufcs completion.
Rainer, I so
On 06.11.2013 03:01, Manu wrote:
I just found something surprising.
I went into the 0.3.37 options, saw the 32bit/64bit separation, but
noticed by default, the lib paths were populated like so:
32bit:
$(DevEnvDir)..\..\VC\lib\amd64\
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Lib\x64
I just found something surprising.
I went into the 0.3.37 options, saw the 32bit/64bit separation, but noticed
by default, the lib paths were populated like so:
32bit:
$(DevEnvDir)..\..\VC\lib\amd64\
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Lib\x64
64bit:
$(VCInstallDir)\lib\amd64
C:\P
Thanks so much. As I've said before, this is an absolutely critical, yet
often overlooked piece of the ecosystem.
Good to see plenty of life in the project! :)
Note: I saw Alexander Bothe released an update to the parser one day after
your release... ;)
On 3 November 2013 00:40, Rainer Schuetze
On Sunday, 3 November 2013 at 08:07:41 UTC, Rainer Schuetze wrote:
I tried to reproduce (within VS2012 Shell) but could not
produce any crashes.
Do you have updates for VS 2012 installed? Did you switch back
to the "old" engine by enabling "native Edit and Continue"
(watches don't work with t
On 03.11.2013 01:34, TheFlyingFiddle wrote:
First of all i would like to thank you for making this wonderfull
plugin. It was the existance of this pluggin that made me even consider
learning D.
This release however broke my setup. Whenever i tried to step into code
while debugging it would cra
First of all i would like to thank you for making this wonderfull
plugin. It was the existance of this pluggin that made me even
consider learning D.
This release however broke my setup. Whenever i tried to step
into code while debugging it would crash visual studio. I fixed
this by changing
Hi,
it's been a long time since the last release of Visual D, but I hope it
wasn't too long. As Visual D moves closer to the dlang.org website, this
is the final release that will be available on
http://www.dsource.org/projects/visuald. Downloads and documentation are
also available at http:/
34 matches
Mail list logo