Skip to main content

Hi!

I found a Bug in Visual Cobol 2.3 Update 2:

Open a Project, then right Mouse and Properties..

Klick on in German "Einstellungen" (The last Point...)

There you can unpdate insert etc. your own Variable...

If you will Change the Name, on the first Time Visual Studio will go down...

On the next Time is is on every klick (Change the Name or insert or what ever) in comming everytime the Message:

After any Chage Visual Studio is going down...

I hop you can fix this...

I test this under Visual Studio 2012 and 2015

Best Regards

Bernd


#VisualCobol2.3Update2Bug

Hi!

I found a Bug in Visual Cobol 2.3 Update 2:

Open a Project, then right Mouse and Properties..

Klick on in German "Einstellungen" (The last Point...)

There you can unpdate insert etc. your own Variable...

If you will Change the Name, on the first Time Visual Studio will go down...

On the next Time is is on every klick (Change the Name or insert or what ever) in comming everytime the Message:

After any Chage Visual Studio is going down...

I hop you can fix this...

I test this under Visual Studio 2012 and 2015

Best Regards

Bernd


#VisualCobol2.3Update2Bug

Hi Bernd,

I can reproduce the problem but I get a different message about operation not implemented when I try to change the name of a string under settings but Visual Studio does not crash.

Can you please open up a support incident with Customer Care so that we can write it up as a bug?

Thanks.

Hi!

I found a Bug in Visual Cobol 2.3 Update 2:

Open a Project, then right Mouse and Properties..

Klick on in German "Einstellungen" (The last Point...)

There you can unpdate insert etc. your own Variable...

If you will Change the Name, on the first Time Visual Studio will go down...

On the next Time is is on every klick (Change the Name or insert or what ever) in comming everytime the Message:

After any Chage Visual Studio is going down...

I hop you can fix this...

I test this under Visual Studio 2012 and 2015

Best Regards

Bernd


#VisualCobol2.3Update2Bug

Hi Chris,

I open an incident about that...

Terms & ConditionsAccessibility statement