Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
Use shared .targets file to set common projet properties - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Fri Aug 4th, 2017 07:39 am
PM Private Upload Quote Reply
jg.iconics
Member
 

Joined: Fri Aug 4th, 2017
Location:  
Posts: 6
Status: 
Offline
Hello,

I created a .targets file that contains the following project properties :

<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
    <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
    <IntermediateOutputPath>$(MSBuildProjectDirectory)\..\..\_build\obj\$(MSBuildProjectName)</IntermediateOutputPath>
    <Batch64TargetFrameworkVersion>v4.5</Batch64TargetFrameworkVersion>
    <OutputPath>bin\Debug\</OutputPath>
    <TargetFrameworkVersion>$(Batch64TargetFrameworkVersion)</TargetFrameworkVersion>
    <TargetFrameworkProfile />
    <AppDesignerFolder>Properties</AppDesignerFolder>
    <FileAlignment>512</FileAlignment>
    <SccProjectName>SAK</SccProjectName>
    <SccLocalPath>SAK</SccLocalPath>
    <SccAuxPath>SAK</SccAuxPath>
    <SccProvider>SAK</SccProvider>
    <WarningLevel>4</WarningLevel>
    <ApplicationVersion>10.93.0.0</ApplicationVersion>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
    <DebugSymbols>true</DebugSymbols>
    <DebugType>full</DebugType>
    <Optimize>false</Optimize>
    <OutputPath>$(MSBuildProjectDirectory)\..\..\_build\bin\Debug\</OutputPath>
    <DefineConstants>DEBUG;TRACE</DefineConstants>
    <ErrorReport>prompt</ErrorReport>
    <WarningLevel>4</WarningLevel>
    <TargetFrameworkVersion>v4.5</TargetFrameworkVersion>
    <TargetFrameworkProfile />
    <PlatformTarget>AnyCPU</PlatformTarget>
    <Prefer32Bit>false</Prefer32Bit>
  </PropertyGroup>
  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
    <DebugType>none</DebugType>
    <Optimize>true</Optimize>
    <OutputPath>$(MSBuildProjectDirectory)\..\..\_build\bin\Release\</OutputPath>
    <DefineConstants>TRACE</DefineConstants>
    <ErrorReport>prompt</ErrorReport>
    <WarningLevel>4</WarningLevel>
    <TargetFrameworkVersion>v4.5</TargetFrameworkVersion>
    <TargetFrameworkProfile />
    <PlatformTarget>AnyCPU</PlatformTarget>
    <UseVSHostingProcess>false</UseVSHostingProcess>
    <Prefer32Bit>false</Prefer32Bit>
    <DocumentationFile>$(MSBuildProjectDirectory)\..\.._build\bin\Release\IcoFrBatch$(MSBuildProjectName).xml</DocumentationFile>
  </PropertyGroup>
</Project>

As you can see, the target framework version is set in this file.

The I import my file "Common.targets" in all projects of my solution, therefore I removed the flag <TargetFrameworkVersion> from all the .csproj. All works fine when I build the solution in Visual Studio 2015.

Now I have to build the resources of the solutions. I am using Sisulizer 3. When I build the resources, I have the followings errors that indicate it could not find the target framework version :

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5): warning MSB3267: The primary reference "System.Xaml", which is a framework assembly, could not be resolved in the currently targeted framework. ".NETFramework,Version=v2.0". To resolve this problem, either remove the reference "System.Xaml" or retarget your application to a framework version which contains "System.Xaml"
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5): warning MSB3267: The primary reference "Microsoft.CSharp", which is a framework assembly, could not be resolved in the currently targeted framework. ".NETFramework,Version=v2.0". To resolve this problem, either remove the reference "Microsoft.CSharp" or retarget your application to a framework version which contains "Microsoft.CSharp"
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5): warning MSB3267: The primary reference "System.Core", which is a framework assembly, could not be resolved in the currently targeted framework. ".NETFramework,Version=v2.0". To resolve this problem, either remove the reference "System.Core" or retarget your application to a framework version which contains "System.Core"
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5): warning MSB3267: The primary reference "System.Xml.Linq", which is a framework assembly, could not be resolved in the currently targeted framework. ".NETFramework,Version=v2.0". To resolve this problem, either remove the reference "System.Xml.Linq" or retarget your application to a framework version which contains "System.Xml.Linq"
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5): warning MSB3267: The primary reference "System.Data.DataSetExtensions", which is a framework assembly, could not be resolved in the currently targeted framework. ".NETFramework,Version=v2.0". To resolve this problem, either remove the reference "System.Data.DataSetExtensions" or retarget your application to a framework version which contains "System.Data.DataSetExtensions"
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5): warning MSB3267: The primary reference "WindowsBase", which is a framework assembly, could not be resolved in the currently targeted framework. ".NETFramework,Version=v2.0". To resolve this problem, either remove the reference "WindowsBase" or retarget your application to a framework version which contains "WindowsBase"
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5): warning MSB3267: The primary reference "PresentationCore", which is a framework assembly, could not be resolved in the currently targeted framework. ".NETFramework,Version=v2.0". To resolve this problem, either remove the reference "PresentationCore" or retarget your application to a framework version which contains "PresentationCore"
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5): warning MSB3267: The primary reference "PresentationFramework", which is a framework assembly, could not be resolved in the currently targeted framework. ".NETFramework,Version=v2.0". To resolve this problem, either remove the reference "PresentationFramework" or retarget your application to a framework version which contains "PresentationFramework"

My solution uses the Framework v4.5.

Can you help me please ?

Back To Top PM Private Upload Quote Reply

 Posted: Fri Aug 4th, 2017 07:57 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2995
Status: 
Offline
To my knowledge this has been addressed in Sisulizer 4. Can you please give it a shot with the eval.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Fri Aug 4th, 2017 08:11 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3741
Status: 
Offline
Markus.Kreisel wrote: To my knowledge this has been addressed in Sisulizer 4. Can you please give it a shot with the eval.

Markus
If you use licensed Sisulizer 3, you can install eval version of Sisulizer 4 to other location (you need select other installation directory and Sisulizer user folder) and check if this version resolve your issue.

Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Fri Aug 4th, 2017 08:21 am
PM Private Upload Quote Reply
jg.iconics
Member
 

Joined: Fri Aug 4th, 2017
Location:  
Posts: 6
Status: 
Offline
Thanks for your quick reply.

I will try with Sisulizer 4. I will give a feedback after the test.

Back To Top PM Private Upload Quote Reply

 Posted: Fri Aug 4th, 2017 09:06 am
PM Private Upload Quote Reply
jg.iconics
Member
 

Joined: Fri Aug 4th, 2017
Location:  
Posts: 6
Status: 
Offline
That does not work with Sisulizer 4. I sent to you a sample project that illustrate the issue.

The target Framework use when compiling resources is Framework 2.0 whereas I use the 4.5

Last edited on Fri Aug 4th, 2017 09:08 am by jg.iconics

Back To Top PM Private Upload Quote Reply

 Posted: Fri Aug 4th, 2017 09:09 am
PM Private Upload Quote Reply
jg.iconics
Member
 

Joined: Fri Aug 4th, 2017
Location:  
Posts: 6
Status: 
Offline
How to send to you a zip file ?

Back To Top PM Private Upload Quote Reply

 Posted: Fri Aug 4th, 2017 10:59 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2995
Status: 
Offline
Use the private upload button right above this post.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Fri Aug 4th, 2017 11:18 am
PM Private Upload Quote Reply
jg.iconics
Member
 

Joined: Fri Aug 4th, 2017
Location:  
Posts: 6
Status: 
Offline
OK, I sent the file. Did you reveived it ?

Back To Top PM Private Upload Quote Reply

 Posted: Fri Aug 4th, 2017 11:25 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2995
Status: 
Offline
Yes, we have to look into it but are rather busy at the moment.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Aug 7th, 2017 09:51 am
PM Private Upload Quote Reply
jg.iconics
Member
 

Joined: Fri Aug 4th, 2017
Location:  
Posts: 6
Status: 
Offline
Can you say me when you can check the file please. I will need to build new resources for my project and it will very help me If i can use the .targets file.

Back To Top PM Private Upload Quote Reply

 Posted: Mon Aug 7th, 2017 02:28 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3741
Status: 
Offline
Hello,

I've already forwarded this issue to our developer and .NT expert. Lat's wait on his investigation.

Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

Current time is 08:50 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Use shared .targets file to set common projet properties



WowUltra modified by Sisulizer Copyright © 2007-09 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Sisulizer software localization tool - Three simple steps to localize