Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Tuesday, July 1, 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: Build issue
Jeff Ballard
Posts: 326
 
Build issueYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 11 Dec 09 11:15 AM
I get the following error when building the web platform.

C:\Documents and Settings\\Sage\Platform\Output\Sage.SnippetLibrary.CSharp\src\Sage.SnippetLibrary.CSharp.@.d878b8ae-89a7-4cc9-84f1-c21e66a82ce2.codesnippet.cs::Keyword 'this' is not valid in a static property, static method, or static field initializer

The problem is the code snippet that contained what was reported error has long been removed it.

Anyone know where this might be that I can remove it? I thought it might be something in memory, but I rebooted, so it's in a db field or file somewhere but I can't find it. And if I delete the referenced file, when I build, it comes back.

For the record, it deploys and runs fine, so I have no idea what's going on.

Jeff
[Reply][Quote]
Raul A. Chavez
Posts: 1300
Top 10 forum poster: 1300 posts
 
Re: Build issueYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 11 Dec 09 11:29 AM
Did you try doing a Full Rebuild (Hold down CTRL key ?).

Where did you delete the file from / how? Did you deleted it from the Output folder? If so, it will be resent as you are rebuilding.
You will have to go into the VFS and find the reference to this item and remove it from there.

Also, when you do a Deploy, it uses that last set of Binaries generated, thus the fact that it appears to work correctly.
[Reply][Quote]
Jeff Ballard
Posts: 326
 
Re: Build issueYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 11 Dec 09 2:44 PM
Raul,

I did delete the file from the output folder on a lark, thinking it would get regenerated, but hoping it wouldn't. It did get regenerated as you said.

The full rebuild didn't get rid of the problem. It has to be in the VFS somewhere, but I can't find it.

Jeff
[Reply][Quote]
Raul A. Chavez
Posts: 1300
Top 10 forum poster: 1300 posts
 
Re: Build issueYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 11 Dec 09 2:57 PM
it may be hard to track. If your VFS is on the DB, you may try search for that GUID on the Name column and see if you get any matches.
If not, maybe you should export your VFS to file and do a search within the File contents.

Another way that has helped me on some ocassions is to go back to the Property of the Control where the Code was originally added and make sure that it is completely clear of any references, sometimes it may still have a reference on it. Maybe switch the handler to a different type of action.
[Reply][Quote]
Jeff Ballard
Posts: 326
 
Re: Build issueYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 14 Dec 09 2:09 PM
I looked in the properties and couldn't find anything. I did a compare between the VFS on my file system and an export of the default VFS in the DB and found a reference to it in the modelindex.xml. I manually edited that and it solved the problem. Of course, I may have broken something else although all seems OK.

Thanks for your help!

Jeff
[Reply][Quote]
Mark Dykun
Posts: 297
 
Re: Build issueYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 15 Dec 09 7:02 AM
Jeff, Model Index is a re-generatable file so removing the file or the entry should be fine. I personally always work from a LFS (local file based vfs) and not a database one. I will purge the output files in the users folder and also locate the smart part/code file that is offending ensuring that they are both removed. I have been having less of a problem with this issue since getting onto 7.5.2 though.

Mark
[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): 7/1/2025 6:26:58 PM