2
Vote

VL locks my source files

description

Im doing an investigation on VL to determine if its usefull for us.

When I run the batch mode I find hardcoded strings that need to be update. For example change string concatenation to string formatting

"my " + name + " " + lastname
to
string.format("my {0} {1}", name, lastname)

etc etc

When I go to my sourcecode file with the issue I need to resolve I see the soucefile is locked (lock symbol). When I close my batch window the lock symbol is removed, but I still cannot edit my sourcecode. I need to close and reload my solution to be able to edit the source files again. This makes the whole process a lot harder.

Any idea what is wrong?

comments

cre8or wrote May 20, 2015 at 4:22 PM

Hi,

when the Batch Move to Resources Window is open, all related files are locked by design, you can double-click on the table rows in the window to show the string in code. This means that the rows have the position of the string stored and editing the file would render these values incorrect.
The files should be unlocked when all Batch Move to Resources WIndows are closed. If this is not happening, then it's a bug - which version of VS are you using?

Regards,

cre8or

njannink wrote May 20, 2015 at 4:28 PM

Im using Visual Studio Ultimate 2013 Update 4

Closing the batch mode window is not releasing my source files. And I even had the issue that starting batch mode again was giving an error in the area of process already active. So maybe the batch mode is not exited correctly after closing the window.

monty24 wrote Jan 25, 2016 at 3:25 PM

With VS2015, the files are released when exiting batch mode. Nonetheless, I think that postponing locking the files till they really need to be immutable is better.

In a typical first round, we replace the strings by hand by methods (we do not use resources, we use an alternative mechanism which better suits our targets). In the second round, all remaining untranslateable resources are marked with VL_NO_LOC.

So keeping the files editable till you really need to "Execute" is handier. Now we have to do it in another editor.

wrote Jan 25, 2016 at 3:25 PM