Mark_Warren

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-01-21
19:58
2510 views
[Migrated content. Thread originally posted on 18 January 2011]
January 20th 2011 is the launch day for Visual COBOL R3 - a major milestone in the evolution of COBOL development and deployment (OK, sorry for the marketing-speak!)Let's use this thread to capture your feedback. Once you've downloaded and installed the product, let us know about your experience.
1 Solution
Accepted Solutions
Scot Nielsen

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-01-28
09:11
Steve and I did get to the bottom of this and he's now up and running with R3.
In brief, the issue is that msbuild will inherit system environment variables which in most cases is fine and desirable. However, in this case there was a clash with an environment variable named VERBOSE and the COBOL msbuild task property also named Verbose.
Unsetting VERBOSE fixed the problem for Steve.
In brief, the issue is that msbuild will inherit system environment variables which in most cases is fine and desirable. However, in this case there was a clash with an environment variable named VERBOSE and the COBOL msbuild task property also named Verbose.
Unsetting VERBOSE fixed the problem for Steve.
4 Replies
stevodevo

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-01-21
20:08
hi there - the product looks awesome and VS integration is great compared to what we've been using.. I'm sampling the product and running this: Tutorial: Developing and Debugging a Native COBOL Application
One issue, I'm getting an error when I try to build the sample program:
Error 1 "1" is an invalid value for the "Verbose" parameter of the "Cobol" task. The "Verbose" parameter is of type "System.Boolean". C:\Program Files\MSBuild\Micro Focus\Visual COBOL\v1.0\MicroFocus.COBOL.targets 304
Any suggestions?
thanks!
One issue, I'm getting an error when I try to build the sample program:
Error 1 "1" is an invalid value for the "Verbose" parameter of the "Cobol" task. The "Verbose" parameter is of type "System.Boolean". C:\Program Files\MSBuild\Micro Focus\Visual COBOL\v1.0\MicroFocus.COBOL.targets 304
Any suggestions?
thanks!
Scot Nielsen

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-01-21
20:22
Hi Stevodevo, could you zip up the test project you are using and send it to scot.nielsen@microfocus.com?
In the interim, if you create a new native console or link library application you may be able to continue with the tutorial.
Thanks.
In the interim, if you create a new native console or link library application you may be able to continue with the tutorial.
Thanks.
stevodevo

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-01-21
21:32
hi Scot, thanks for the quick response. You should be getting that email shortly. Sorry I failed to mention in my original post that the tutorial I'm having problems with is the one in the MicroFocus help.
thanks
thanks
Scot Nielsen

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2011-01-28
09:11
Steve and I did get to the bottom of this and he's now up and running with R3.
In brief, the issue is that msbuild will inherit system environment variables which in most cases is fine and desirable. However, in this case there was a clash with an environment variable named VERBOSE and the COBOL msbuild task property also named Verbose.
Unsetting VERBOSE fixed the problem for Steve.
In brief, the issue is that msbuild will inherit system environment variables which in most cases is fine and desirable. However, in this case there was a clash with an environment variable named VERBOSE and the COBOL msbuild task property also named Verbose.
Unsetting VERBOSE fixed the problem for Steve.