I'm unable to find previous releases of NoesisGUI. I wanted to try the UE4 shooter game example, but it requires a older version of NoesisGUI and UE4, and I can no longer find that old version for download. Is there any possibility you could keep the links for historic releases around? Or atleast keep all the dependencies needed in the samples?

Older versions are provided to customers in private download folders. Right now, we are not offering this for Indie users. What we should do is updating that example to the latest version of Noesis and Unreal. Could you please open a ticket about it?

Sure, will do. I did eventually figure things out on my own. Importing the view from Xaml in the newer version worked with no issue, but I did not know how to support custom types (for the stuff like death messages). I did figure it out on my own eventually, and I now have the in-game hud working (though i did it somewhat differently, using C++ and UObjects for the view models, as I'm still new to UE and blueprints and find the workflow a bit slow).

Having worked with Xamarin.Forms and WPF in the past, this was very easy to get into, and when I eventually figured things out it was a really great experience. It could be nice to have some documentation or maybe a sample on how to get started with C++ in UE, as I could only find blueprint based samples in the sample collection.

Really great product, looking forward to see how it will evolve

Thanks for the kind words.

We should definitely add a specific sample for C++ without blueprints. The only pure C++ example is the one about UserControls. For the documentation, almost all the tutorials for C++ SDK are valid for Unreal. The Unreal tutorial includes the specific additions. But it is true what we should improve the organization.

Taking notes of everything, thanks for the suggestions.

This has been really annoying over the years since I have had to manually maintain a pipeline to do what you already have behind the scenes. Any chance we can just make this a modern universal for everyone so that we can just version pin directly via UPM in unity without the extra hassle of each studio setting up their own CI/CD pipeline to do this and monitor your site for downloads etc? I mean this with respect, the current approach just feels very `legacy` :)

Thanks for your feedback!

Better integration with the package manager in Unity has been considered in the past, and perhaps this is a good opportunity to revisit it for NoesisGUI 4.0.

Could you please elaborate on what your ideal pipeline for integrating NoesisGUI into Unity would look like?

Here is what I really want:
- ability to have historical versions for pin/rollback, without having to monitor and archive myself.
- ability to easily drop that in via url to UPM, private git repo would be fine
that's pretty much it :)

Once you have that bare minimum of that history + UPM friendly git repo or whatever you choose to serve it up in a UPM compatible way, I can easily handle automating the rest like license setup etc in the CI/CD stuff that's custom to the project.

If it's a matter of bandwidth, then all I really need is your permission and I can set it up for you if you want (for free, I just love your team), I can give you scripts for a Buildkite pipeline or github or whatever you want to do to keep it secure/cheap/easy to maintain and share with license holders, I basically just need a folder of zips with your old versions and whatever rules from your end (only logged in people should be able to see it, etc, etc).

TLDR: basically once you generate a new version artifact ready for us, I want to be able to get it via a UPM friendly URL, and I want the old versions around too so that I'm not forced to latest because of a lack of history.

I was experimenting with a scoped registry, and it more or less works. However, having this on GitHub would be much better. If I understand correctly, though, when using GitHub as a source for the Unity Package Manager, there’s no automatic detection of new versions, right? The user has to manually refresh or update the patch version to get a new release, etc

If I understand correctly, though, when using GitHub as a source for the Unity Package Manager, there’s no automatic detection of new versions, right? The user has to manually refresh or update the patch version to get a new release, etc

The way it works is you will get the latest by default. I will use https://github.com/Cysharp/R3 as an example since Cysharp org and `neuecc` (Yoshifumi Kawai) are extremely competent across the board, and this is a very beautiful example of a more exotic UPM package that even involves NuGet (but you can ignore the nuget stuff for our discussion right now).

In the Unity section:
https://github.com/Cysharp/R3#unity

You will see step 2:
`Install the R3.Unity package by referencing the git URL`
https://github.com/Cysharp/R3.git?path= ... s/R3.Unity

It's that simple! So we have a lot of options for getting it in, including a local clone/fork whatever and doing git+file, or direct git, scoped registry, whatever you imagine :)

Some companies just give access to the repo basically you get an invite to your account/org and then you can maintain your private mirror or reference it directly after cloning, skipping the overhead of scoped registries entirely (i think some older unity version had support issues with scoped registries too just fyi but I might be wrong, might be something to think about if you're targeting very old LTS though, keeping it simpler might be a win)

If a user wants a specific version of Noesis they would do something like what R3 suggests in their example:
`R3 uses the ..* release tag, so you can specify a version like #1.0.0. For example: https://github.com/Cysharp/R3.git?path= ... nity#1.0.0`

I hope this helps answer your question?

Related and in case you want to check manual for older versions to make a judgement call on how you want to offer repo access, via scoped registry or something else:
https://docs.unity3d.com/6000.6/Documen ... ncies.html
https://docs.unity.cn/6000.1/Documentat ... coped.html
https://docs.unity3d.com/6000.6/Documen ... pdate.html

Some people also use https://openupm.com/ for handling this stuff, I'm putting it on your radar, but I don't personally find myself reaching for or needing it considering how simple the overall process of publishing a package is once you have the actual artifacts prepared properly, but I could see maybe some exotic situations being made easier with OpenUPM pipeline stuff maybe. I'll leave that up to your judgement :)