During the upgrade of my ASP-project the references in the aspx-files are revised. The problem is that the utility seems to change the file encoding and all none ASCII characters are screwed up. Is this just a "bug", is it a known issue and is there a workaround for it? I did upgrade the project in the past with no problem. I cant use the utility to upgrade any ASP project right now.
I'm upgrading form IG 9.2 to 10.3. The project is a Visual Studio 2008 SP1 project, I'm using Framework 3.5 and the operating system is Win7 in German.Any help is appreciated.Uli
Hello Uli,
This is a known issue with the new version of our upgrade utility. For a workaround, can you try to save your files in UTF8 or Unicode encoding before upgrading? You can do this by opening the file, choosing File > Advanced Save Options, and selecting a Unicode encoding. Once you do that, please make sure that the non-ASCII characters appear correctly, and then proceed with the upgrade.
Let me know if this doesn't solve the problem.
Elizabeth AlbertLocalization Engineer
Thank you for that info! I'll try the workaround next time. In general changing the encoding is a problem since we use TFS and rely on file comparison tools that often have problems comparing file with different encodings. Hope this bug is soon be fixed.Uli
The version less controls would be the best solution. (So the aspx files wouldn't have to be changed at all.) For me I thing the promblem is that we are using framework 3.5 and the version less controls are only available for 4.0?
Hello Ulrich,
After doing further research I found “version less assemblies for 3.5 assemblies” is a feature request. I have created a feature request 12866 on your behalf. I have sent your feature request directly to our product management team.
I will provide more details on this feature request through private support case.
Thanks,
Bhadresh
Hello uli,
Yes, that's correct. Our help says that the versionless assemblies will always be compiled against the latest CLR version, which would be 4.0.
I will forward this post to the developer in charge of the version utility. In the meantime, please use Unicode encoding for any upgraded projects.