I've just updated this post but still need help and clarification!
I'm creating small packages for a project that add specific functionality to the site when installed - this installation, for the most part, is working fine, but I'll cover the issues I'm facing in a moment.
First, as a burgeoning package developer, I've read all that I can - all the links in this article and plenty of others here on Our - and have implemented Richard Soeteman's recommended PAC.dll into my packages.
Can anyone expand on the current state of the issues raised in Matt Brailsford's post from 2010 on the best way to use PAC as far as namespacing and versioning goes for the .dll and future updates?
Namely, do I need to create a "package specific" PAC.dll and if so, how?
Second, The issues I'm running are mainly when I try to update the packages I've created and am testing them on my local test site:
The version updates don't show on the site - even after a restart of either IIS or VS (IIS Express), AND it seems that the DocumentTypes that have been changed and repackaged are NOT applied on an update package install?
Is there a better way to "patch" a package or to force a document type to update?
When I try to uninstall said update it removes files referenced in the package code but not included in the package itself- which causes other issues with the site like content disappearing?
Is there a way to keep files only referenced by said package to NOT be removed on package uninstall?
The version links in the back-office Package information don't do anything other than change colour on hover - what are they supposed to do?
Any help on this one would aid the understanding of these links!
I've just found Tom Fulton's Skrift article on using Grunt to package things up but wonder if this process will help with the versioning issues stated above?[Not applicable but good info!]
I've written my own actions, and they live in the "Package Actions" root directory - I've added the .dll as it seemed that the actions wouldn't fire without this or is this my misunderstanding of its use?
With the version links/numbers, I have incremented the packages in the acceptable manner outlined by Git, but as I said in the post neither the back-office links nor the updated document types seem to be doing anything?
Thanks for taking the time to help, it's greatly appreciated and I look forward to any additional thoughts!
yes you have to add the dll in your package thats right.
Have you added them in the textarea for package actions? When you create/manage your package there is a field where you have to add them to let Umbraco run them. It's some kind of xml markup and I think you also have to add in which assembly they are. But not sure.
Haven't used them in a while.
For the links, if I am right then they are just links by markup not because they have a behavior related to a link. So don't bother with them beeing links.
I've used Richard Soeteman's Package Action Tester to verify the actions I've created work on my dev environment and they pass. I'm confused as to why some parts, namely document types, included in the package updates aren't being applied?
I'll have a stumble around to see what's up with the version links and their purpose...
Package Creation and Updating
Hey all,
I've just updated this post but still need help and clarification!
I'm creating small packages for a project that add specific functionality to the site when installed - this installation, for the most part, is working fine, but I'll cover the issues I'm facing in a moment.
First, as a burgeoning package developer, I've read all that I can - all the links in this article and plenty of others here on Our - and have implemented Richard Soeteman's recommended PAC.dll into my packages.
Can anyone expand on the current state of the issues raised in Matt Brailsford's post from 2010 on the best way to use PAC as far as namespacing and versioning goes for the .dll and future updates?
Second, The issues I'm running are mainly when I try to update the packages I've created and am testing them on my local test site:
The version updates don't show on the site - even after a restart of either IIS or VS (IIS Express), AND it seems that the DocumentTypes that have been changed and repackaged are NOT applied on an update package install?
When I try to uninstall said update it removes files referenced in the package code but not included in the package itself- which causes other issues with the site like content disappearing?
The version links in the back-office Package information don't do anything other than change colour on hover - what are they supposed to do?
I've just found Tom Fulton's Skrift article on using Grunt to package things up but wonder if this process will help with the versioning issues stated above?[Not applicable but good info!]Thank you everyone!
Hi Jon,
i would recommend not to use the PAC.DLL and instead write the package actions you need yourself. So you don't rely on a certain DLL version.
The version number shouldn't do anything as far as I know.
Regards David
@David,
I've written my own actions, and they live in the "Package Actions" root directory - I've added the .dll as it seemed that the actions wouldn't fire without this or is this my misunderstanding of its use?
With the version links/numbers, I have incremented the packages in the acceptable manner outlined by Git, but as I said in the post neither the back-office links nor the updated document types seem to be doing anything?
Thanks for taking the time to help, it's greatly appreciated and I look forward to any additional thoughts!
Cheers,
J
Hi Jon,
yes you have to add the dll in your package thats right. Have you added them in the textarea for package actions? When you create/manage your package there is a field where you have to add them to let Umbraco run them. It's some kind of xml markup and I think you also have to add in which assembly they are. But not sure. Haven't used them in a while.
For the links, if I am right then they are just links by markup not because they have a behavior related to a link. So don't bother with them beeing links.
Regards David
@David,
I've used Richard Soeteman's Package Action Tester to verify the actions I've created work on my dev environment and they pass. I'm confused as to why some parts, namely document types, included in the package updates aren't being applied?
I'll have a stumble around to see what's up with the version links and their purpose...
J
is working on a reply...