Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Sunday, February 23, 2025 
 
slxdeveloper.com Community Forums  
   
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
 Web Forums - SalesLogix Web Platform & Application Architect
Forum to discuss the use of the SalesLogix Web Platform, Client and Customer Portals, and the Application Architect (For version 7.2 and higher only). View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to SalesLogix Web Platform & Application Architect | New ThreadView:  Search:  
 Author  Thread: Reducing Build and Deploy Time using the SLX 7.2 Application Architect
Ezi Porbeni
Posts: 11
 
Reducing Build and Deploy Time using the SLX 7.2 Application ArchitectYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 09 Jul 08 9:41 AM
I'm sure a lot of us are sick with this but I want to ask this again simply and hopefully get a simple definitive answer.

Working in the AA, when I make a change I have to build the web platform and then deploy it just to test my change. This entire process easily takes at least ten minutes.
1) Is there anyway around this without using VS or anything else but the AA?
1a)Any way to rebuild and deploy just the parts involved in my change?
2) Any chance that if there is no way around this currently, that there will be in the next version of SLX?
3) Ok any way around this that does involve VS or something other than AA (remember less than ten minutes from change to testing change)?
[Reply][Quote]
Ezi Porbeni
Posts: 11
 
Re: Reducing Build and Deploy Time using the SLX 7.2 Application ArchitectYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 10 Jul 08 11:32 AM
Working in the AA, when I make a change I have to build the web platform and then deploy it just to test my change. This entire process easily takes at least ten minutes.
1) Is there anyway around this without using VS or anything else but the AA?
1a)Any way to rebuild and deploy just the parts involved in my change?
2) Any chance that if there is no way around this currently, that there will be in the next version of SLX?
3) Ok any way around this that does involve VS or something other than AA (remember less than ten minutes from change to testing change)?

Answer for #3)
Well you can edit the ascx file(for whatever part you are working on) with notepad (or visual webdev, or any other editor that works), save it and refresh the web page to see the changes immediately. It is IMPORTANT to NOTE that a) This method allows you to make and test changes instantly (e.g., working on the account detail form, aka AccountDetails.ascx file) but the changes will NOT be preserved permanently - once you've firgured out what you need you MUST still go back into AA and make your changes there. b)Your editor of choice may not have intellisense features (notepad) so you could be coding raw while testing - I still used AA for it's intellisense to check myself.
I would guess that someone else already knew this and there might be a way to use an editor that does inherit\expose Sage classes and thus provides intellisense type features - if so please share. Perhaps my questions were too elementary but still... please share.
[Reply][Quote]
Stephen Redmond
Posts: 190
 
Re: Reducing Build and Deploy Time using the SLX 7.2 Application ArchitectYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 10 Jul 08 5:28 PM
Hi Ezi,

If you don't have VS then you can use Visual Web Developer Express Edition to run and debug SLX web sites.

A little better than notepad and free to download.



Stephen
[Reply][Quote]
Ryan Farley
Posts: 2265
slxdeveloper.com Site Administrator
Top 10 forum poster: 2265 posts
 
Re: Reducing Build and Deploy Time using the SLX 7.2 Application ArchitectYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 10 Jul 08 6:52 PM
Quote:
Originally posted by Ezi Porbeni

Well you can edit the ascx file(for whatever part you are working on) with notepad (or visual webdev, or any other editor that works), save it and refresh the web page to see the changes immediately. It is IMPORTANT to NOTE that a) This method allows you to make and test changes instantly (e.g., working on the account detail form, aka AccountDetails.ascx file) but the changes will NOT be preserved permanently - once you've firgured out what you need you MUST still go back into AA and make your changes there. b)Your editor of choice may not have intellisense features (notepad) so you could be coding raw while testing - I still used AA for it's intellisense to check myself.
I would guess that someone else already knew this and there might be a way to use an editor that does inherit\expose Sage classes and thus provides intellisense type features - if so please share. Perhaps my questions were too elementary but still... please share.


I do it this way all the time. Make changes directly to the deployed site, even to the source code in the build output folder, then you see the changes right away and if it works I just go back and add my changes into the appropriate places in teh AA. Much faster

BTW, when I build a deploy it only takes me about <2 minutes, not 10. Not sure why it is taking you so long. Is this on a VM with low resources or something?
[Reply][Quote]
 Page 1 of 1 
  You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

   Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2025 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 2/23/2025 8:26:49 PM