Home
»
RC-WinTrans Support
»
Problem with NETFilesConverter.macro file
For support issues and specific questions related to RC-WinTrans' use, features and functions.
24.11.2015 06:15:33
Jan Bronka
Posts: 6
|
Hello,
Regularly, after killing RCWinTrans10.exe file 'NETFilesConverter.macro' is destroyed and in result next start of RCWintrans finishes with crash.
When file will be overwritten from copy (orginal after installation) again, for some time, all is fine.
RCWinTrans10 need to be killed becase usage of automation mode case problems with closing process (even in samples there is possibility to kill process).
What can we do with this problem ?
|
|
0
• permalink
|
24.11.2015 11:11:22
Support
Administrator
Posts: 245
|
Hello jbronka,
three questions:
.
1. " ... 'NETFilesConverter.macro' is destroyed "
How does this looks like? Is the macro file deleted/removed?
2. " ...killing RCWinTrans10.exe file "
What do you do when "killing" RC-WinTrans? How?
3. "... because usage of automation mode "
What is your "automation mode"?
Command line? Using RC-WinTrans as COM server from e.g. a C# application? Other?
Regards,
Support, Schaudin.com
edited by Support on 24.11.2015
|
|
0
• permalink
|
24.11.2015 11:23:51
Jan Bronka
Posts: 6
|
Answering your questions...
1. NETFilesConverter.macro size is significantly bigger than orginal, It is binary file I do not know what is inside however I had to add to my process restoring this file from copy to have stabil result. If you wish I can deliver to you "damaged" file.
2. I use WMI to kill RCWinTrans10.exe but similar efect I had by killing using TaskManager
3. COMAutomation mode - this is excactly what RWTCmd.exe is doing. In my particular case I have VBS script and inside I just use RCWinTrans.Application object
My current process is working in the following way (this is part of build process):
...
1. create lock (to guarantee other build process will not access RCWintrans becasue version 10 does not support it... Version 7 works perfectly)
2. kill RCWinTrans10.exe (sometimes process hangs [of time of closing is too long])
3. restore file NETFilesConverter.macro
4. perform translation process of one library (write all target files)
5. close RCWinTrans
6. kill RCWintrans10.exe (to do not have hanging processes)
7. restore file NETFilesConverter.macro (to do not leave not working RCWinTrans)
8. go to point 2 and perform another library
9. when all libraries were translated release lock
...
There is redundant killing and restoring but it is very fast compare to translation process and give me clean process...
|
|
0
• permalink
|
24.11.2015 18:27:52
Support
Administrator
Posts: 245
|
.
1.
> NETFilesConverter.macro size is significantly bigger than orginal, ...
>
RC-WinTrans updates a VBA Reference in the NETFilesConverter.macro file. Usually this increases the size of macro file a little bit.
But: The file is not demaged.
You can avoid this...
a) set the file attribute of the "NETFilesConverter.macro" to "Read-only".
or
b) remove/delete the macro file .\RC-WinTrans 10\Add-Ons\VBAReferenceCheck.macro
2.
> ... [of time of closing is too long])
>
Wait. It takes some seconds (it depends, 10-60) until the .NET Garbage Collection will and has released all objects.
There are very many .NET objects and COM objects allocated and used by RC-WinTrans.
A kill process should not be necessary.
Regards,
Support, Schaudin.com
edited by Support on 24.11.2015
|
|
0
• permalink
|
24.11.2015 19:48:27
Jan Bronka
Posts: 6
|
Thanks for you answers I will try to check these ideas
|
|
0
• permalink
|
Powered by AspNetForum 6.9.6.0
© 2006-2010 Jitbit Software