We are currently running v3.30 and we have the need to add pagination in a few admin pages, so we were wondering if it is worth reusing the grid or go for a new one.
We are currently running v3.30 and we have the need to add pagination in a few admin pages, so we were wondering if it is worth reusing the grid or go for a new one.
Thanks in advance !
We're still going to use Telerik in the near time. Currently there's no good replacement
P.S. Please subscribe to this topic in order to keep informed if we decide to move to other UI framework
I'm not clear about what is the approach you're taking to support Azure, are you moving with traditionals IIS, Web solution(VM) or cloud Services, in Azure?
I'm not clear about what is the approach you're taking to support Azure, are you moving with traditionals IIS, Web solution(VM) or cloud Services, in Azure?
thanks !
Hi Richard,
No, traditional IIS will always be supported. Azure is also alrady supported. We want to add support for multiple instances in Windows Azure (web farms support). Find more info here
Regarding the "Better warehouse support and inventory control", please make it so it doesn't drop the old table or records because we still have it with valuable warehouse contact information and credentials.
Hi breakskater,
There is a thread on the inventory control/warehouse stuff here.
As Andrei suggested I made a rather substantial post on the base table structures that IMO would be needed to do it correctly but for some reason no one seems to want to talk about it even though I offered my dev time to make it happen.
That said in analysing the table structure changes that would IMO be needed I had given significant thought to retaining historical data, in the structure I propose the existing tables would remain but some fields in existing tables would be moved to other tables.
The crux of the outcome would be that all existing data would be retained abet re-engineered for the new structure.
Is this what you had in mind or do you have customised reports or functionality that would be adversely affected with the upgrade path I propose?
Could we move to the next generation of Web, Single page application, migrating from server side to client side to give user better UI experience. Angularjs, RequireJS, breezejs,... man the whole bunch of new trend, even on Visual studio, there's more and more new SPA templates in new updates.
http://easyspa.azurewebsites.net/
http://cc-ng-z.azurewebsites.net/#/
Also i found http://www.aspnetboilerplate.com/ is a solid enterprise infrastructure to start with.
Is this what you had in mind or do you have customised reports or functionality that would be adversely affected with the upgrade path I propose?
Hey Gaz, I reviewed your recommendations for the multiple warehouse feature and it sounds thorough and all will be implemented except the shelf feature. I do not think there would be an adverse affect as long as there is a migration/upgrade script that is ran to move the data from the existing structure to the new structure.