Converting PKT Subassembly to a DLL

[cyberflow]

Hi all,

Looking forward onto converting PKT's we've done into DLL's.

Just trying to figure out if there's an easy way to do so, or is it a teadious task to do so ?

Thank you in advance for guiding me a bit on this

[hippe013]

A pkt file is just a renamed zip file. Rename the extension to ".zip" and then extract its contents. Is this a pkt file created with Subassembly Composer and if so, what year? 

[cyberflow]

Hi @hippe013 

Your right, PKT is simply a zipped file with several files.
Just trying to find a way to pre-install on several PKT's by creating and using a DLL instead

They're done with SAC 2023 and some SAC 2024

[hippe013]

---

@cyberflow wrote:

Just trying to find a way to pre-install on several PKT's by creating and using a DLL instead

---

I guess I am not sure what you mean. 

[cyberflow]

Hi @hippe013 

Well, our department wants to push some custom PKT we've done.

So that's what we're trying to accomplish - Finding a way to point on our servers per departement their respective PKTs.

We were thinking maybe : 

-Using the DLL's generated by the import of the PKT's so that each user won't need to Import PKT's
-Putting the DLL's in a network location so it's accessible by everyone in their respective teams

Hope i'm a bit more clearer now what i'm trying to accomplish.
Maybe i'm looking at the wrong place and there's a workflow that works in another way.

[cyberflow]

Hi @pollygler,

Thx for the reply but what is Worktango ?

[nkiakas]

Hi @cyberflow

DLL as dynamic linked library, in fact what it has?

Has part of the source code with a way to don't be "visible" to other user.

I guess the need is to be able to share pkt file, without allowing the user to reuse the pkt file, for commercial purposes?

[GTVic · Accepted solution]

The PKT import process automates a number of steps you can do yourself. One way to do this is to look at the created files after importing all your subassemblies, primarily the tool palette ATC file. I believe C:\ProgramData\Autodesk can be on the network as part of your Civil 3D deployment.

1. Subassembly DLL files go in a location such as C:\ProgramData\Autodesk\C3D 2023\enu\
2. Subassembly help files go in a location such as C:\ProgramData\Autodesk\MyCompanySubassemblies\
3. Deploy a pre-configured Tool Palette containing the already imported subassembly entries
   1. This is an ATC file containing all subassembly parameters
   2. The ATC contains the DLL name and help file location
   3. The DLL is automatically found if located correctly as above
4. You can deploy a preconfigured workspace that includes Tool Palette Groups with already loaded palettes. Otherwise the user has to locate the provided palette on their own.