[CLOSED] Examples.ext.net is pointing to V2 beta. Request to keep Examples explorer for both

Hi,

Today I noticed that https://examples1.ext.net is showing the 2.0 Beta examples explorer. While it is great that the beta is coming through is it possible to keep https://examples1.ext.net showing your current 1.0 version?

The reason is that there are thousands of links (from your own forums) to specific examples from Ext.NET 1.0 to examples.ext.net and now a lot of them are broken. I see for example, many posts from Daniil, Vladimir and Geoff often refer to those 1.0 examples, and I expect a number of people will be on 1.0 for a while until 2.0 is released. Keeping those links alive will help a lot with trouble-shooting.

Although many of us can just as easily compile and run the same examples explorer locally, it is also good to see it publicly so it can be accessed by those who can't have it locally for whatever reason.

There is already an https://examples2.ext.net so perhaps that can remain for v2?

Thanks!

Quote:

---

Originally Posted by anup

Hi,

Today I noticed that https://examples1.ext.net is showing the 2.0 Beta examples explorer. While it is great that the beta is coming through is it possible to keep https://examples1.ext.net showing your current 1.0 version?

The reason is that there are thousands of links (from your own forums) to specific examples from Ext.NET 1.0 to examples.ext.net and now a lot of them are broken. I see for example, many posts from Daniil, Vladimir and Geoff often refer to those 1.0 examples, and I expect a number of people will be on 1.0 for a while until 2.0 is released. Keeping those links alive will help a lot with trouble-shooting.

Although many of us can just as easily compile and run the same examples explorer locally, it is also good to see it publicly so it can be accessed by those who can't have it locally for whatever reason.

There is already an https://examples2.ext.net so perhaps that can remain for v2?

Thanks!

---

Hi Anup,

All the v1 samples are available at the https://examples1.ext.net/ domain.

We're working on a way of switching between the app versions. Almost all the link locations have not died, although they have changed versions. We're looking into some ideas to make this switching more seamless.

Hi all,

Just thoughts: maybe, replace all "https://examples1.ext.net" with "https://examples1.ext.net" on the forums?

Seems, there are already some links with "https://examples1.ext.net" regarding to Ext.NET v2, but it should not be a big problem.

Quote:

---

Originally Posted by Daniil

Just thoughts: maybe, replace all "https://examples1.ext.net" with "https://examples1.ext.net" on the forums?

---

You beat me to it Daniil..!

Geoff, thanks for the link, too. It is good that there is an examples.1ext.net and that is the way forward. But Daniil's suggestion would be great, if at all possible as there are some links which do break (though maybe not most, as I initially thought, thankfully).

The other issue is context: if a forum post reply is saying to see an example for how to do something, it is currently likely about the v1 examples. So the old post now linking through to a newer version can be disorienting. Especially if someone is new to Ext.NET.

Sorry for additional post; just thought of another alternative/issue:

If we do update the links that will work for short term. It will then mean Ext.NET v2 links to examples will be to examples.ext.net and for now will work without problem. But when v3 is on horizon, the same problem will occur again.

So perhaps the following is workable?

• Maybe always make examples.ext.net redirect to examples1.ext.net? (Might have to be done at JavaScript level because of the need to preserve the bit after the # fragment in the URL which the server won't see and you want to redirect to specific example not just the root).
• Then, always use example{n}.ext.net where n is the version. This way forum posts (and other links) now and in future will always point to the right version.
• Maybe on all supported example explorers that are not the latest version, have some big text in the header linking to latest version?
• If someone visits examples.ext.net directly (i.e. the root, without any #) then you might have more flexible options, e.g. use it as a "landing page" to provide a huge link to the latest/current version of the examples explorer and smaller links to other versions.

We have added the link between two Examples Explorers (at the top on the right).

Regarding to your last suggest. At the first of all - thanks for your time to post.

Personally, it would be the best to keep "examples.ext.net" for v1, make "examples2.ext.net" for v2, will make "examples3.ext.net", etc. Seems, there would not be any problems at all.

Though I'm not sure how much important to make "examples.ext.net" for the last/current version.

Geoffrey should read your post, but for sure I will notice him myself.

We've made a few changes which should help avoid some confusion in the Examples Explorer.

1. The goal is always maintain the default Examples Explorer location (https://examples2.ext.net/) as the most current official Final release. The change to Ext.NET v2 is a little early (still Beta), but we really want to focus on the v2 release going forward (it's just that much better), so the decision was made to push v1 into the sub-domain (https://examples1.ext.net).

2. A new button has been added to the header of both Examples Explorer v1 and v2. Clicking in v2 (https://examples1.ext.net) will redirect to the v1 Examples Explorer (https://examples1.ext.net). Clicking in v1 will redirect to v2.

3. All old "https://examples1.ext.net" links in the forums have been updated to "https://examples1.ext.net". The new v2.x forums/posts were not modified, so any links within the v2.x (Premium and Community) will still point to their original location.

4. Eventually when we're ready to update to v3.x, all "https://examples1.ext.net" links will be updated to "https://examples2.ext.net" and the cycle will continue.

5. We're also investigating auto rendering a "version switcher" header bar into each of the examples, if they're not rendered within the main Examples Explorer parent app. For example, when browsing without the hash /#/ in the path.

Hope this helps.

Thanks for all the suggestions.

Sorry for my delayed reply

Thanks for the the explanation. Sounds great.

P.S. awesome that you think v2 is "just that much better" :)