A detailed explanation on how this page works is available here
Basically the idea is to implement each page as a C# class possibly in a dll that provides the mark-up that is dropped into an <asp:literal>
is very out of fashion at the moment and whilst I don't think that most businesses need to copy Google and create Go or
Facebook and create React, they also don't need to copy what they did, instead they should do what is right for their business.
When you have a big IT department it is
quite easy to use various technologies and not have to worry about staff having the necessary skills or configuring servers.
With small departments the
cost of extra languages and frameworks can be very high, training and familiarity take time, only Fred understands that and he is off this week
so can you make do with what
Because a lot of my background is with hardware makers
writing code rather than looking for it on the internet is normal for me. Just writing what you need is often better and cheaper for your business in the long term.
Pop onto StackExchange and see how many people are saying something like
I've spent two days on this problem, why doesn't it work
and the answer is You need to set property Version="2021"
even though you have 2022 because the dependency FredWhoHasLostInterest hasn't been updated and doesn't recognise 2022
Or even worse the package
is still supported and they have decided that iPhone x.x is no longer supported and that is critical to you.
You may think that I am being silly on this but I am surprised just now many sites don't work with an iPhone 5. I don't mean some state of the art feature,
I mean something like a pop-up when you first visit the site which takes up the whole of the screen and you can't dismiss it or a menu that doesn't do
Obviously if you retain control you can do most of your pages in the most productive way and then handle any special cases the
Pinging iansmithcse.co.uk [220.127.116.11] with 32 bytes of data:
Reply from 18.104.22.168: bytes=32 time=68ms TTL=114
Reply from 22.214.171.124: bytes=32 time=75ms TTL=114
Reply from 126.96.36.199: bytes=32 time=2382ms TTL=114
Reply from 188.8.131.52: bytes=32 time=736ms TTL=114
Ping statistics for 184.108.40.206:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 2382ms, Average = 815ms