I didn't know you could set properties on a feature via powershell. That is pretty cool. I think we are going to just have to agree to disagree with the coding it within VS then recreate it in PowerShell. If you are experience with PowerShell, then yes, simply create it only in PowerShell. However, if you are new to PowerShell and dont know the syntax, then do it in VS first, then convert it to PowerShell. An inexperience PowerShell developer could easily learn how to convert simple C# syntax into PowerShell. In my experience, when I was trying to configure search for a SharePoint environment, I wanted to use PowerShell. I started off doing it in PowerShell and I could not figure out how to initially code it without any intellisense. Yes PowerGui does offer some intellisense but not for the deep search configurations. Therefore, I created it in VS first. It was even difficult to do within VS. I finally got it to work inside VS and then moved it to a Powershell script.

Chris

That is true. But there are limitations to features. 1. You cannot configure a feature. You can only simply turn it on and off. Problem: Well what if you wanted the administrator who deploys the solution and wants change the name of the "sub site" or what if you wanted the administrator to dynamically add and remove the number of "sub sites" that should be created on deployment. You cannot do that with a feature. Sometimes all information is not known when creating functionality. 2. You have maintenance issues. Say a web feature (say FeatureA) that when you turn it on creates a list (say ListA). Sounds great. You even make it so that list can only appear on the root of the site collection. O Ya Problem: That feature is still present in ALL web sites within the farm/web application that you deployed it to. This means that any web administrator (they do not have to be a site collection administrator) can activate that feature on other site collections. Well, you say "so what. Thats not a problem". Well you then leave the company and the company is rearranging their portal. They decide to get rid of ListA because its no longer needed. So they deactivate the feature on the root site collection and remove the solution. O, but wait, what about the feature that some web administrator was playing around with in a different site collection. Now that list may not have a list definition. You are now getting calls from random web administrators say they can no longer get to "View All Site Content". The list definition that was removed was actually being used. Thats just great!!! 3. Feature Nightmare? Say you create 100's of these features over the years that simply create lists. These features are now all within all your site collection features and web site features when they do not need to be. WHY IN THE WORLD IS THERE A FEATURE FOR CREATING A LIST, WHEN IT IS JUST A ONE TIME DEAL WITH POWERSHELL!!!!For example, I am seeing features to create a "Toyota List 1", "Toyota List 2", "Toyota List 3" in my "GMC" site collection. Well what if you had a toyota site collection, GMC site collection, Ford site collection, and 40 other site collection. What a nightmare this could be for maintaining features which could confuse site collection administrators. I would say carefully analyize you business requirements and make a proper decision as to whether or not powershell should be used or a feature should be used. Features are easier but could have drawbacks. I said create the initial solution as

Good point.

Chris

If it is a one time deal I would suggest using powershell. Most of time I actually build out the steps within a feature because you have intellisense and it is just easier. Then when I am sure that the feature is working, I convert it into a Powershell script.

Chris

This is possible to do a "no code" solution, but it would probably be a lot of work. You could use SharePoints web services and JavaScript/JQuery to accomplish this. I would suggest using the content query web part to get the list to show on the page. Then after that you JQuery to allow the user to select rows they wish to modify and autopopulate a form (built in HTML or JQuery) with a submit button. When the user presses the submit button call the web service to update or add an item. You could also use JQuery to insert a delete button next to the items in the content query web part so when the user presses a delete button it will call a web service to remove the item from the list. If you do use the content query web part another approach would be to manipulate the item.xsl to automatically render a delete button for you. You could also manipulate other xsl files to create the form and submit buttons. You do have some options to choose from but I do think it is possible. Check this link out.

Chris

Simple question here. Did you verify that all your picture libraries are crawlable. Check in the Picture Library settings.

Chris

It has been a while but yes you can accomplish this. I have done a codeless InfoPath form when submitted it will actually send data to multiple lists. I beleive you have to connect to the lists within the info path form first. Then drop all the lists onto the InfoPath form. Now you should have all the fields from all the lists showing on the InfoPath form. Thats the easy steps. Next you have to open the XSLT for the InfoPath form and manually move the fields that you want from one list area to another list area. I think that is how I did it. I am not 100% sure. I think I also experimented with dropping a list on an InfoPath form and then hiding it. Next you can drop a text box on the form that when a user hits submit, it can copy the context of the box into the field (which is hidden) for a specific list. Again sorry about such a generic solution. I hope this gives you some ideas on what you might look into for solving your problem.

Chris

You would probably be better off talking to a Microsoft representative because there are different licenses for SharePoint 2010, SQL Server 2008, etc. The representative should assist you with this information.

Chris

Were you able to solve you issue?

Chris

Mark is right. I dont think you can do just change the setting within IIS to point to a different directory. How many pages are you going to have within your root site? Is it just the home page that is within the different directory or is it a bunch of pages within the root directory?

Chris

Your issue has been fixed?

Chris

No this is a SharePoint 2007 environment.

Chris

I am trying to write a custom web service that is in its own web application that also has its own application pool. When trying to open the site collection using SPSite site = new SPSite("https://www.abc.com"), I get the following error message: (System.IO.FileNotFoundException = The Web application at https://www.abc.com could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.). Now if I change the application pool to the SharePoint application pool everything works just great. There is a different identity on my new application pool, but I have verified that this identity has access to the site collection. Also, I am running the code within an SPSecurity.RunWithElevatedPrivileges block.

SPSecurity.RunWithElevatedPrivileges(delegate
{
using (var site = new SPSite("https://www.abc.com"))
{
using (var web = site.OpenWeb("/Test"))
{
...
}
}
});

Does anyone have any suggestions? If this is not possible could you point me to an msdn article that states it is not possible? Thanks,

Chris

The only thing that I could think of is that you may want to pass the IDs through a single parameter to the child report. When you build your SQL Query for the parent report, one of the columns that are returned could contain ALL the child IDs (separated by a comma). Then through a subreport parameter you could transfer this parameter that contains all the child IDs into the query for the subreport. I think this could be accomplished a lot easier if you use the RDLReportViewer[^] control instead of having to write all that .NET code to accomplish this. With using the RDLReportViewer[^] control you can just simply create a parent and child RDL file and the RDLReportViewer[^] control could easily show the RDL reports by telling the RDLReportViewer[^] control what report to show. It will automatically run all the queries and display the user parameters[^]. Check it out...

Chris

Thanks for the response. I am so glad someone else is using this besides me. I do have another question. With the databases that you mention, none of them require attaching addition dlls? For example, MySql doesn't require you to install some sort of .NET Component Installation and then attach those .NET DLLs to your solution so a user can then use MySql? Or is that automatically included within the enterprise library like SqlServer? What about Cache?

Chris

Try the WebClient class...

Chris

I have an application that uses the Enterprise Application Block 3.1. Yes I know there is an Enterprise Application Block 4.0 and 5.0 that is now available. I cannot use these applications blocks because they require the 3.5 .NET Framework. Anyway, I know that the Enterprise Application Block 3.1 uses the DbConnection class and I am curious as to which databases this supports? I could not find this anywhere in MSDN. I think some database connections require custom classes that derive from the DbConnection class but I am after a list of databases that the Enterprise Application Block 3.1 will automatically handle without the implementation of custom classes?

Chris

I really dont know if this is the best place to ask this question but here it goes... Background Information: I am creating template C# 2008 web sites that contain different modules. I may have web sites A, B, C, D, etc that each contain different modules. A module could be a couple different things. It could be a GUI change such as a side panel on the main web page like in code project on the left where it says chapters, Announcements, etc. Another example could be new web pages like a shopping cart with paypal or google checkout. Another would be web site polling such as the one on www.PollPro.com while would be code changes and additional web pages. A module could mean C# server side code changes to files, HTML code changes, and or including of files that dont exist, and or changes to the SQL Server the web site is using. The Question: What is the best way to start accomplish this in a very maintainable way? Possible Answers: 1. Create a base web site that contains no modules at all. Then within the code place sections that could be between commented sections like // GOOGLECHECKOUTMODULE_BEGIN and // GOOGLECHECKOUTMODULE_END. Then build an application that will remove all the sections and a specified list of files if the module is not selected. The problem with this is that other modules could be using the same files. Another problem is that this project would become a maintaince nightmare with all the different commented sections. 2. Create a base web site that contains no modules at all. Then copy that project and add only one module. Then when a module is selected the two projects need to be merged together. This would include merging files and adding files that dont exist. Merging coded files may be a little work but is possible. If different modules contain the same file name that needs to be added then which one is used? Any other options?

Is it even possible to use an Olap database with an MDX query to retrieve data? I am trying to do this with the Microsoft.Practices.EnterpriseLibrary.Data.Database object. My first problem begin when using the System.Data.Common.DbProviderFactories object and calling the function GetFactory("Microsoft.AnalysisServices.AdomdClient"). I am getting an exception saying "Unable to find the requested .Net Framework Data Provider. It may not be installed.". I have installed SQLServer2005_ADOMD.msi so I should have this client installed right? Please help... Chris

That is what I was looking for... Thanks