Codejock Forums Homepage
Forum Home Forum Home > Codejock Products > Visual C++ MFC > Toolkit Pro
  New Posts New Posts RSS Feed - VS 2017 Toolkit Project file incorrect for 18.3.0.
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

VS 2017 Toolkit Project file incorrect for 18.3.0.
 Post Reply Post Reply
Author
Message
  Topic Search Topic Search  Topic Options Topic Options
lviolette View Drop Down
Groupie
Groupie
Avatar

Joined: 17 March 2007
Location: United States
Status: Offline
Points: 62 		Post Options Post Options   Thanks (0) Thanks(0)   Quote lviolette Quote  Post ReplyReply Direct Link To This Post Topic: VS 2017 Toolkit Project file incorrect for 18.3.0.
    Posted: 20 April 2018 at 11:47pm
If you open CodeJock\Xtreme ToolkitPro v18.3.0\Workspace\ToolkitPro\ToolkitPro_vc150.sln in VS 2017.
Then go to Configuration Manager.

Choose "Unicode Release | x64" in the Active Solution Configuration/Platform.
Note that it shows the following:
Codejock.ToolkitPro.Shared - Unicode Release - x64
Codejock.ToolkitPro.Static - Static Unicode Release - x64

Now choose "Unicode Debug | x64" in the Active Solution Configuration/Platform.
Note that it shows the following:
Codejock.ToolkitPro.Shared - Unicode Debug - x64
Codejock.ToolkitPro.Static - Dynamic Unicode Debug - x64

Codejock.ToolkitPro.Static suddenly went to "Dynamic" Unicode Debug.  I would expect it to go to "Static" Unicode Debug.

Anyone else see this?  I believe it should go to Static Unicode Debug.
L. Violette
Monolith
www.lith.com
Xtreme Toolkit Pro v22.1.0
Back to Top
lviolette View Drop Down
Groupie
Groupie
Avatar

Joined: 17 March 2007
Location: United States
Status: Offline
Points: 62 		Post Options Post Options   Thanks (0) Thanks(0)   Quote lviolette Quote  Post ReplyReply Direct Link To This Post Posted: 23 April 2018 at 2:35pm
I posted this in the general forum.  But I think it was the wrong place to post this as it's specific to a problem with Toolkit Pro.

Open main CodeJock solution file in VS 2017:
Xtreme ToolkitPro v18.3.0\Workspace\ToolkitPro\ToolkitPro_vc150.sln

Go to Configuration Manager.

Choose "Unicode Release | x64" in the Active Solution Configuration/Platform.
Note that it shows the following:
  • Codejock.ToolkitPro.Shared - Unicode Release - x64
  • Codejock.ToolkitPro.Static - Static Unicode Release - x64

Now choose "Unicode Debug | x64" in the Active Solution Configuration/Platform.
Note that it shows the following:
  • Codejock.ToolkitPro.Shared - Unicode Debug - x64
  • Codejock.ToolkitPro.Static - Dynamic Unicode Debug - x64

Codejock.ToolkitPro.Static suddenly went to "Dynamic" Unicode Debug.  I would expect it to go to "Static" Unicode Debug.

Anyone else see this?  I believe it should go to Static Unicode Debug.  Can anyone confirm this isn't my setup and what this should be set to?
L. Violette
Monolith
www.lith.com
Xtreme Toolkit Pro v22.1.0
Back to Top
olebed View Drop Down
Admin Group
Admin Group


Joined: 01 July 2014
Location: Ukraine
Status: Offline
Points: 841 		Post Options Post Options   Thanks (0) Thanks(0)   Quote olebed Quote  Post ReplyReply Direct Link To This Post Posted: 24 April 2018 at 2:57am
Hello,

For "[Unicode] Debug/Release" have sense only configuration of  Codejock.ToolkitPro.Shared.

Codejock.ToolkitPro.Static project used only for "Static/Dynamic [Unicode] Debug/Release" compilations.

I always use separately Codejock.ToolkitPro.Shared and Codejock.ToolkitPro.Static projects.

Your changes can be introduced only to be consistent.

Regards,
 Oleksandr Lebed
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.281 seconds.