Re: Macros in User Defined Tool not working?
1. I am using 4.1.3 U. I think that is most recent one. 2. Example: $(FileDir)build.bat. Sure it can be done by setting "Start Folder" to $(FileDir) and Command to build.bat . It is just nice to have feature if for some reason you would need "Start Folder" to be different from where Command is executing. 3. My current output is "Csc: : ERROR LINE: D:\projects\etc.translator\src\xtraneng\edi\validator\axInfoItem.cs(76,78): The name 'segm' does not exist" (no quotes). Having ability to define simple parser rule OR use build-in already existing rules would be ideal 4. Inability to close OutputWindow with simple shortcut becomes important when you make more than 10 builds per day. And if you are making >100 like me that really becomes important.
|