Hi everyone,

I'm hoping somebody here will be able to help me in my SLX endevours.  I am trying to do customizations for the web client using Application Architect and I noticed that sometimes I need to modify the resulting ascx/aspx files manually because not all code generated from the Application Architect is actually error free (go figure ).  Typically what I would do is do a deployment, then open up the file in Visual Studio, edit it, save, and move on, but this is not an effective method because every time there is a new deployment all of the changes get overwritten resulting in a lot of manual code management.  Is there any way that the changes can be done through Application Architect in a way that would propagate the same permanently through the code base or am I SOL?

With that said, the second question that I have pertains to working off of a local file system.  How can I set things up to work off of a local file system instead of the VFS and then integrate the same changes back into the VFS for deployment?

Finally (for now), can anybody explain to me the differences between various workspaces (e.g., tab, detail) and views (entity, portal, and main view) in SLX web client/Architect and when I should be using each.

Thanks!

Rather than taking a class on\Through this forum, what research have you done on the web? DevLogix, Ryan's articles, Mark Dykun, Nic Galler, SLX, Help About, looking at other customized forms......

Suffice it to say that most of us work within Visual Studio against a File System....deploy the file system to the websites and all is good. You debug IN the test\dev website.....and when something is running stunningly tasty you can paste it back into the dev File System.

Their are quite a few therapists making money off of Application Architect frazzled developers....

Quote: Originally posted by Dejan Horgas Hi everyone, I'm hoping somebody here will be able to help me in my SLX endevours.  I am trying to do customizations for the web client using Application Architect and I noticed that sometimes I need to modify the resulting ascx/aspx files manually because not all code generated from the Application Architect is actually error free (go figure ).  Typically what I would do is do a deployment, then open up the file in Visual Studio, edit it, save, and move on, but this is not an effective method because every time there is a new deployment all of the changes get overwritten resulting in a lot of manual code management.  Is there any way that the changes can be done through Application Architect in a way that would propagate the same permanently through the code base or am I SOL? With that said, the second question that I have pertains to working off of a local file system.  How can I set things up to work off of a local file system instead of the VFS and then integrate the same changes back into the VFS for deployment? Finally (for now), can anybody explain to me the differences between various workspaces (e.g., tab, detail) and views (entity, portal, and main view) in SLX web client/Architect and when I should be using each. Thanks!

Hi Dejas,

For the second question...using the Project Workspaces area at the bottom of App Architect you can create a new local VFS workspace and import from the main VFS. The method we use to get the changes back into the main VFS is to simply bundle them, log into the main VFS and apply the bundle.

Depending on what you are changing for the first question the answer is more than likely no, you wouldmnt be able to make the changes without getting them overwritten by a deploy. What are you changing out of interest?

THanks,

Nick

Hi Dejas,

What I do is to have more than one deployment. For example, a IIS deployment to show the customer the "stable" releases and other File System deployments that I work on using Visual Studio. I open the File Systems deployment from VS, make my changes running the website with VS and when they're Ok, I move them to the "Portal\SlxClient\SupportFiles" folder of the Model (I always have the Model on the file system).

Using several Files System deployments you will never have to overwrite your customizations.

Regards,

     Marcos

Thanks for the answers so far.  It looks like everyone recommends working off of the local file system.  I will try to move stuff out of the VFS and onto the local system today and see how that goes.  Problem is that I do not have a test environment set up locally, but I will see if I can get one going.  I have been working exclusively on our development server so far where everything is already set up.

In regards to the one question that was posted wondering what it is that I need to modify, one example that I ran into consistently so far is the Data Source control class.  This class is WebEntityListBindingSource part of the Sage.Platform.WebPortal.Binding library.  The Application Architect consistently calls the constructor for this class using 2 arguments, however no such override constructor exists.  The class only accepts 0 or 4 arguments.  This means that any time I create a Data Source on a form I am forced to modify the code to properly call the class constructor otherwise I get runtime errors.

Looking forward to more tips and tricks!