| bio | website | bloggoergosum.com |
|---|---|---|
| location | United States | |
| age | 33 | |
| visits | member for | 3 years, 2 months |
| seen | Sep 10 '12 at 16:12 | |
| stats | profile views | 18 |
I work for Stack Exchange.
I am a professional developer, formerly in the "Defense & Aerospace" industry. I was daily entrenched in embedded real-time systems, signal processing, C, Git, C++, C#. My side projects involve Lisp, C#, concurrency and distributed systems, algorithms, math. Sometimes, when my wife is mad at me and my kids won't hug me, I do webby stuff. But I don't tell anyone. I later worked for a small .NET/Sharepoint consulting agency in Dallas, followed by a time with a startup in Dallas.
|
Mar 19 |
comment |
Provision listview webpart on page layout using feature The issue may be there - the announcement list is located in each subweb of /myserver/sites/mysite. The idea is to have the welcome page for each of those sites provisioned with all the default webparts on it. Perhaps it would be better to just do this in a WebProvisioned event. |
|
Mar 15 |
comment |
Add WebPart to page and lock it down (except for editing) Yeah, ok. That may wind up being the answer. A RichHtmlField is certainly simpler than trying to deploy and restrict a webpart. |
|
Mar 14 |
comment |
Add WebPart to page and lock it down (except for editing) @PaulLucas to which controls are you referring? |
|
Mar 7 |
comment |
Is there a way to set permissions so that a content editor part can be edited but not removed from the page? Well, I don't think a Wiki page is the right answer for this particular scenario, but I was thinking of putting a rich text area in a page layout. Users would have to have edit permissions to change it, but they wouldn't be able to remove it from the page. |
|
Nov 16 |
comment |
Aggregate Content Types Right, but what I'd like to accomplish is building a single form for the user where an order and all of its line items can be entered together. If I go the two-list route, then my order list forms and views would have to be pretty heavily customize, right? |
|
Nov 15 |
comment |
Can fieldrefs in content type definitions change the internal name of a site column? I think you're right. I changed the internal name in the content type and re-generated the list template and it seems to work. I'm still having problems with the list instance, but that's a separate issue. |
|
Nov 14 |
comment |
Creating a Site collection programmatically throws exception <nativehr>0x80070005</nativehr> I tried to edit, but I don't have permissions yet. Question title should have "programmatically", and the exception message and ULS log could use some formatting. |
|
Nov 9 |
comment |
Why won't my site column deploy from an elements file? Alright. I found this: Solution Deployment : Missing one or more of the following attributes from the root node in solution XXXXXXX.wsp: assembly '', type ''. According to the internets this is an ambiguous message that means roughly something like "your sandboxed solution contains unsupported somethings-or-other". One person had restricted code, and another suggested it might be unsupported attributes in the Field element. Not sure what they would be. |
|
Nov 9 |
comment |
Why won't my site column deploy from an elements file? No error. The column just doesn't appear in the Site Column Gallery. |
|
Nov 8 |
comment |
Can site columns be deployed in sandboxed solutions? @RobWindsor I went back and duplicated what Hilton did in the video, and it worked as shown. I tried then to duplicate the results with an empty project and adding an empty elements template item, and couldn't get it to work, although as best I could tell the resulting packages should have been identical. Next step: actually tear out the WSPs to see what the difference is. |
|
Nov 8 |
comment |
Can site columns be deployed in sandboxed solutions? @AndyBurns good point. You're probably right about that. |
|
Nov 8 |
comment |
Can site columns be deployed in sandboxed solutions? @RobWindsor: yeah, that's exactly what I did and it didn't work for me. Hrmmm... |
|
Nov 8 |
comment |
Can site columns be deployed in sandboxed solutions? Yes, I've seen that video. What I don't like about it is that he starts with a content type element, and I don't think I should have to do that (I followed the same steps, except with an elements file instead of a content type, and it didn't work). Have you ever successfully deployed a site column in a sandboxed solution just using an elements file? |
|
Oct 31 |
comment |
Error occurred in deployment step 'Add Solution': Sandboxed code execution request failed (but no implementation at all) I changed the setting as suggested, and it appears to have worked. However, my farm is a standalone installation (and a fresh installation), so why would this work now and now before? |
|
Oct 31 |
comment |
Error occurred in deployment step 'Add Solution': Sandboxed code execution request failed (but no implementation at all) @JamesLove nothing. |
|
Feb 21 |
comment |
Can't delete site columns that aren't referenced there is an OOTB column called "Start Date". |
|
Nov 30 |
comment |
SharePoint list template repackaged, forms now unavailable (“cannot get ghost document”) Hah. I tried to upvote you, but I don't have enough reputation. :-) |