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: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
SDK not found - 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: Wed Jun 16th, 2010 10:37 am
PM Private Upload Quote Reply
liam
Member
 

Joined: Wed Jun 16th, 2010
Location: Dublin, Ireland
Posts: 3
Status: 
Offline
I keep getting the following error when importing a source or when building a localised DLL even though I have the SDK (2.0 and 4.0) installed.

11:14:31 Warning Could not read component hierarcy for the form: %s No .NET SDK found. Choose Tools | Platforms | .NET -> Versions to set the SDK directory.


The mappings on Tools|Platforms|.Net are correct. I am running version 2010 build 306 on Windows 2003.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 16th, 2010 10:56 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 1900
Status: 
Offline
Hi,

You are sure you have the .NET SDK and not just the .NET runtime installed?

Markus




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

 Posted: Wed Jun 16th, 2010 11:04 am
PM Private Upload Quote Reply
liam
Member
 

Joined: Wed Jun 16th, 2010
Location: Dublin, Ireland
Posts: 3
Status: 
Offline
Yes, I am. And I have tried uninstalling Sisulizer and installing again, rebooting the machine, creating new projects, from different locations etc.

Liam

Last edited on Wed Jun 16th, 2010 11:06 am by liam

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 16th, 2010 11:27 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 1900
Status: 
Offline
Hi,

Can you please upload the sources you try to scan. Please zip them and also include your Sisulizer project (.slp).

Please use the "Private Upload" button right above this post. It helps us to keep track of uploads and forums posts.

Markus




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

 Posted: Wed Jun 16th, 2010 01:01 pm
PM Private Upload Quote Reply
liam
Member
 

Joined: Wed Jun 16th, 2010
Location: Dublin, Ireland
Posts: 3
Status: 
Offline
Files uploaded!

Just want to be clear that I am able to import the file and build the localised assembly but the message I reported is always displayed.

Thanks

Liam

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jun 16th, 2010 01:18 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 1900
Status: 
Offline
Hi,

I could reproduce the issue. I think the warning is just wrong or misleading. Even the placeholder is not replaced by a form name. I'll forward this to R&D for a fix.

Thanks for reporting it.

Markus



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

 Posted: Mon Jun 21st, 2010 12:39 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Bedburg, Germany
Posts: 1900
Status: 
Offline
Hi Liam,

I could solve the problem on my system with the help of our R&D the following way.

Close Sisulizer
Locate you .slo file (on Vista or V7 it is in your documents folder under Sisulizer 20xx. Under XP it is in the Sisulizer 20xx app folder)
Create a backup of the .slo
Open the original in notepad
Delete the <net></net> section, e.g.

  <net>
    <net20 sdk="C:\Program Files\Microsoft SDKs\Windows\v6.0A"/>
    <net30 sdk="C:\Program Files\Microsoft SDKs\Windows\v6.0A"/>
    <net35 sdk="C:\Program Files\Microsoft SDKs\Windows\v6.0A"/>
  </net>

Save the .slo file
Start Sisulizer.

Sisulizer now tries to find the paths automatically. Check these paths. They (at least .NET 2) should have the file IldAsm.exe in it. Sisulizer needs this file to read the hierarchy data of your project.

Hope the above will solve your problem.

Markus



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

Current time is 08:17 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 > SDK not found



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