RE: [OzMOSS] RE: Developing for MOSS/WSS with VS2008
I use VSeWSS. I use it for the following reasons. - It is a Microsoft flagship tool for developing sharepoint solutions in visual studio, so it will continue to evolve. - Generates my manifest, feature and solution files (which I can easily customise in WSP view) - Has a number of templates that I find useful. - Custom List based on Custom Content Types - WebPart - EventReceivers - List Definition with .aspx forms - Field Control - does also have more templates... - Solution Generator allows you to pull down List Definitions created in the UI - Has a great documentation with sample code Yes, there isn't a template for every development scenario e.g Custom Actions, but you can add/modify files to cater for these situations. Here is a nice example of creating a couple of .aspx site pages using VseWSS 1.2 http://blogs.msdn.com/cjohnson/archive/2008/06/07/updated-building-a-simple-asp-net-page-based-sharepoint-application-in-visual-studio-with-the-visual-studio-extensions-for-wss-1-2-with-visual-studio-2008.aspx Clayton James -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gavin Barron Sent: Wednesday, 30 July 2008 3:03 PM To: listserver@ozMOSS.com Subject: RE: [OzMOSS] RE: Developing for MOSS/WSS with VS2008 So, Bill, you'd prefer nothing at all from MS?? There are some limitations and the wspbuilder and stsdev tools are good too. I recommend that you try the various tools and find the way YOU like to work, I know a couple of people who are using a combinations of these tools to support their approaches. Anyway to answer your questions Paul 1.How do I get my 32-bit development work from the VM to the 64-bit staging environment (which I understand is supported)? Am I expected to create a solution package for every little modification and then copy it across to that box, open it for testing, then deploy via Stsadm, object model of Central Admin? Yeah, although you can package many features into one solution package. 2.Do I even need VS installed on the remote servers? I hardly see the point if workflow authoring is not supported. Nope. 3.Do I need to deploy my code and assemblies to every web front end manually or does this occur automatically when deploying a solution? Just take the .wsp setup .bat file. Edit the setup.bat file to use -immediate in the deploysolution step followed by an execadmsvcjobs too ;) You should ensure that you supply the correct /weburl and /siteurl values for your target environment. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Williamson Sent: Wednesday, 30 July 2008 4:31 p.m. To: listserver@ozmoss.com Subject: Re: [OzMOSS] RE: Developing for MOSS/WSS with VS2008 IMO the VSE for MOSS are a joke. I know that I am not alone in this, but try not to cause too much trouble :) On Wed, Jul 30, 2008 at 1:30 PM, Paul Noone [EMAIL PROTECTED] wrote: Who would have believed there was no remote API?! And that 64-bit support for the Visual Studio 2008 Extensions isn't even in scope?! OK…I've setup my 32-bit Windows Server 2003 VM with MOSS (a basic site collection), SQL 2005, VS2008 and Extensions 1.2. Great! Now I'm able to launch VS2008 and create a new project (SharePoint Sequential Workflow) without errors. However after much Googling and online reading through other people's posts of misery, I still have a couple of questions: 1.How do I get my 32-bit development work from the VM to the 64-bit staging environment (which I understand is supported)? Am I expected to create a solution package for every little modification and then copy it across to that box, open it for testing, then deploy via Stsadm, object model of Central Admin? 2.Do I even need VS installed on the remote servers? I hardly see the point if workflow authoring is not supported. 3.Do I need to deploy my code and assemblies to every web front end manually or does this occur automatically when deploying a solution? Apologies if I'm not making any sense or just sounding terribly naïve. I'll also look into Hyper-V. Thanks Daniel. Regards, Paul From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Brown Sent: Wednesday, 30 July 2008 12:20 PM To: listserver@ozMOSS.com Subject: RE: [OzMOSS] RE: Developing for MOSS/WSS with VS2008 · Our server is running on 64-bit architecture. I understand that having VS2008 on the same box means you can't deploy solutions. Would it make any difference to stick with 32-bit on the dev environment? I think for the most part the x86/x64 is not too bad in this case, where developing on x86 should work fairly seamlessly. However saying that, I haven't developed code for targeted x64. · Do you develop a VM from scratch and use an empty MOSS environment, or is it better to take a snapshot of your
Re: [OzMOSS] Self Registration on Public Facing MOSS 2007
Hi Al, it is possible using forms based authentication plus some Codeplex extensions in the Community Kit for SharePointhttp://www.codeplex.com/CKS/Release/ProjectReleases.aspx?ReleaseId=7675. It probably doesn't make sense in situations where AD is used natively within MOSS anyway. Regards, Kirk. 2008/7/30 Allan M [EMAIL PROTECTED] Hello, Does MOSS 2007 have the capability for anonymous users to 'self register' themselves to a site? Upon self-registration preferably then could be automatically placed into a specific group whereby they could then contribute to forums and Wiki libraries. All help appreciated. Thanks Al -- Find out: SEEK Salary Centre Are you paid what you're worth? http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext_t=764565661_r=OCT07_endtext_salary_m=EXT --- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com --- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
[OzMOSS] Export site from MOSS to WSS
Has anyone had to export a site from MOSS and then import it into WSS? I had to try to do this and of course it didn't work because WSS doesn't have all the features that MOSS does. Do you know if it will work if I turn off the MOSS features on the MOSS site and then try the export/import again? I don't want to just jump in and try it because I expect the MOSS site will lose funtionality if I turn off the MOSS features - and I only want to do it if I am confident that the export will then work. Cheers, Caroline ** - NOTICE FROM DIMENSION DATA AUSTRALIA This message is confidential, and may contain proprietary or legally privileged information. If you have received this email in error, please notify the sender and delete it immediately. Internet communications are not secure. You should scan this message and any attachments for viruses. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. ** --- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
Re: [OzMOSS] Export site from MOSS to WSS
This will likely depend on what template the site was created from. On Thu, Jul 31, 2008 at 9:32 AM, Caroline Specker (AU) [EMAIL PROTECTED] wrote: Has anyone had to export a site from MOSS and then import it into WSS? I had to try to do this and of course it didn't work because WSS doesn't have all the features that MOSS does. Do you know if it will work if I turn off the MOSS features on the MOSS site and then try the export/import again? I don't want to just jump in and try it because I expect the MOSS site will lose funtionality if I turn off the MOSS features - and I only want to do it if I am confident that the export will then work. Cheers, Caroline ** - NOTICE FROM DIMENSION DATA AUSTRALIA This message is confidential, and may contain proprietary or legally privileged information. If you have received this email in error, please notify the sender and delete it immediately. Internet communications are not secure. You should scan this message and any attachments for viruses. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. ** --- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com --- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
[OzMOSS] RE: Export site from MOSS to WSS
Very good idea. I'll do that. Thanks. From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Ishai Sagi [EMAIL PROTECTED] Sent: Thursday, 31 July 2008 9:46 AM To: listserver@ozMOSS.com Subject: [OzMOSS] RE: Export site from MOSS to WSS How about you export it in moss, import it to a different moss location, and turn off the features in that location? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Caroline Specker (AU) Sent: Thursday, 31 July 2008 9:33 AM To: listserver@ozMOSS.com Subject: [OzMOSS] Export site from MOSS to WSS Has anyone had to export a site from MOSS and then import it into WSS? I had to try to do this and of course it didn't work because WSS doesn't have all the features that MOSS does. Do you know if it will work if I turn off the MOSS features on the MOSS site and then try the export/import again? I don't want to just jump in and try it because I expect the MOSS site will lose funtionality if I turn off the MOSS features - and I only want to do it if I am confident that the export will then work. Cheers, Caroline ** - NOTICE FROM DIMENSION DATA AUSTRALIA This message is confidential, and may contain proprietary or legally privileged information. If you have received this email in error, please notify the sender and delete it immediately. Internet communications are not secure. You should scan this message and any attachments for viruses. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. ** --- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com --- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com --- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
RE: [OzMOSS] RE: Structuring Data in MOSS
Sort of, you certainly could do it that way, but I think it would be less flexible and harder to maintain. If you did it that way every time you added a new contact you would then need to go back to the suppliers list and add them to the appropriate supplier. If you add the lookup column to the contacts list, when you add a contact to the list you specify what supplier they are for at the same time as the rest of the data. Then you also have the ability to create views that use the supplier field on the contacts list (All contacts grouped by supplier, all the contacts for supplier X, All contacts in state X grouped by supplier, etc). Brian Farnhill L2 Consultant Technical Consulting Mobile: 0408 289 303 Fax: 02 8001 7778 Email:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED] Web: www.uniqueworld.nethttp://www.uniqueworld.net Blog: pointstoshare.spaces.live.comhttp://pointstoshare.spaces.live.com/ [cid:image001.jpg@01C8F2F9.A3FBDD30] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of FILMALTER Arno Sent: Thursday, 31 July 2008 10:17 AM To: listserver@ozMOSS.com Subject: RE: [OzMOSS] RE: Structuring Data in MOSS That's what I was thinking, separating the data entities and creating a list for each entity and then linking them together. Basically the same as designing tables but only using lists and content types instead. Suppliers List has lookup field to Supplier Contacts List with multiple selections allowed. Does that sound right? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Farnhill Sent: Thursday, 31 July 2008 10:02 AM To: listserver@ozMOSS.com Subject: [OzMOSS] RE: Structuring Data in MOSS In my opinion it depends on how you are going to use the data once you have recorded it. Think about what the requirements are for how you plan to use the data and that should help you figure out how you should store it. If you want it is possible to break it up into different lists, one that has the suppliers, and one that has all the contacts and this list could have a look up field back to the supplier list to identify what supplier they are tied to. Then you could filter the contacts list per supplier to see a list of all contacts for a supplier, or show them grouped by supplier, or see all the contacts for all suppliers in each state (if you have a field for state), etc etc etc. Brian Farnhill L2 Consultant Technical Consulting Mobile: 0408 289 303 Fax: 02 8001 7778 Email:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED] Web: www.uniqueworld.nethttp://www.uniqueworld.net Blog: pointstoshare.spaces.live.comhttp://pointstoshare.spaces.live.com/ [cid:image001.jpg@01C8F2F9.A3FBDD30] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of FILMALTER Arno Sent: Thursday, 31 July 2008 9:42 AM To: listserver@ozMOSS.com Subject: [OzMOSS] Structuring Data in MOSS Hi Everyone This is just a question of best practices a guess... If I have data like supplier information which I need to capture in MOSS, do I use normal database design principles to outline the columns and types within MOSS or do I just add the required fields into one list or content type? Example: A supplier has name, telno, address ect. But also has Contacts associated to them. With normal database design you will separate the two because it has a one to many relationship between suppliers and supplier contacts. But in MOSS you may add these contacts with their detail in one multi line field within the list or content type. Is there any article or blog that discusses this? My personal opinion is to go with the traditional database design principles. I would really want to know what's been done out there. Regards Arno * Disclaimer * The contents of this electronic message and any attachments are intended only for the addressee and may contain privileged or confidential information. They may only be used for the purposes for which they were supplied. If you are not the addressee, you are notified that any transmission, distribution, downloading, printing or photocopying of the contents of this message or attachments is strictly prohibited. The privilege of confidentiality attached to this message and attachments is not waived, lost or destroyed by reason of mistaken delivery to you. If you receive this message in error please notify the sender by return e-mail or telephone. Please note: the Department of Public Works carries out automatic software scanning, filtering and blocking of E-mails and attachments (including emails of a personal nature) for detection of viruses, malicious code, SPAM, executable programs or content it deems unacceptable. All reasonable precautions will be taken to respect the privacy of individuals as outlined in the DPW Privacy Plan. Personal information will only be used for official purposes, e.g. monitoring
