Check if you have proper master page references.

There is no foolish question, there is no final answer...

Take a look: SPUserPoll[^]

There is no foolish question, there is no final answer...

Your question is not fully clear to me but it appears like you added a new column to a document library but might have missed to include the column in the default view. Anyway, you can include that column in view by modifying the view.

There is no foolish question, there is no final answer...

Are they also getting deleted from the web part gallary as well?

There is no foolish question, there is no final answer...

Mark, I appreciate your remarks. My intention was not to teach you how to create a web part for SharePoint. There is nothing to get ego involved in the knowledge sharing process and get angry right? In codeproject, we share our experiences. Yes, I don't have hesitation to accept that I am unaware about when I should not use ScriptLink control. But, can you please share where exactly I am wrong? When should I not use ScriptLink control and why?

There is no foolish question, there is no final answer...

You can consider using TaxonomyWebTaggingControl in your SharePoint 2010 Webpart. Try out the following link: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.taxonomy.taxonomywebtaggingcontrol.aspx[^]

There is no foolish question, there is no final answer...

Hi Mark & PHC, Though the link which I had shared was related to the SharePoint 2010 Visual Web Part but that did not necessarily mean that ScriptLink is restricted to be used with only Visual Web Part. It can also be used with SharePoint 2010 Standard Web Part quite easily. I know words are not convincing enough few times; so let me give a quick code example: (i) Create a Empty SharePoint 2010 project and add a standard web part into it. (ii) Use the following code block to add a ScriptLink and a Button control:

ScriptLink scriptLink;
Button btnOk;
protected override void CreateChildControls()
{
scriptLink = new ScriptLink();
scriptLink.Name = "test.js";
this.Controls.Add(scriptLink);

btnOk = new Button();
btnOk.Text = "Show Alert";
btnOk.OnClientClick = "javascript:return showMsg();";
this.Controls.Add(btnOk);

}

(iii) In a text editor, create a javascript file (.js) with the following javascript code:

function showMsg()
{
alert('ScriptLink is so easy.');
}

(iv) Save the js file in the following location and name it test.js: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\1033 (v) Finally, deploy and test. I will be waiting for your comments guys. :cool:

There is no foolish question, there is no final answer...

You can use ScriptLink class to register a javascript resource which can be used when the page gets rendered. Checkout the following thread which will give you some idea about how to use ScriptLink: http://social.technet.microsoft.com/Forums/en-US/sharepoint2010programming/thread/3e4caa8d-08ee-40e8-84ea-dec6c988de0e[^]

There is no foolish question, there is no final answer...

Prachee, The following code that you are using is actually instantiating the ASP.NET Login controls:

var loginControl = new Login();

You may not have removed the following namespace:

System.Web.UI.WebControls

For an easy solution, you can consider using a Sandboxed Visual Webpart which gives you an ASCX file where you can add an ASP.NET Login Control. Your ASCX file will be auto embeeded with the Visual Web Part. I just added a Login control in my Sandboxed Visual Webpart and it's coming enabled only. I would like to suggest you to try.

There is no foolish question, there is no final answer...

Are you using the standard asp.net login control? Share the code for the login control.

There is no foolish question, there is no final answer...

Yeah, I agree with you. 5 votes for your comment. Correct me if I am wrong but MugsPat and Prachee G are the same person. So, we are getting a reply from the same person who originally asked the question. As far as our feedback are concerned, people should know what they should do and they should not in CP. That's how a new becomes old. Both Mark and myself shared some links and thoughts to your questions and unfortunately you criticize us by simply voting 1 instead of working on the solutions. Reply back if the links are not useful or if you have any questions. All the best again!

There is no foolish question, there is no final answer...

modified on Tuesday, January 18, 2011 1:53 AM

I completely agree with Mark as you should try at your end first and then come back to us if you have any questions. There is no one in the code project whos is having time or getting paid for giving you the complete steps from start to end. Sometimes people may feel quite harsh when you ask someone to do so in CP. People are here to help you out but not supposed to do your work. For custom login webpart checkout the following link: http://blogs.msdn.com/b/kaevans/archive/2010/07/09/creating-a-custom-login-page-for-sharepoint-2010.aspx[^] Visual Studio 2010 has a great feature to package the source files into a deployable WSP file. For example, create an Empty SharePoint 2010 Project in Visual Studio 2010 and add a WebPart (for your custom login screen). Once you are done with the coding, then right click on the project and click on Package. A WSP will be automatically generated and stored inside bin/debug or bin/release based on the Visual Studio Solution Configuration. I hope that you have some stuffs to start. All the best. :)

There is no foolish question, there is no final answer...

Hi, Are you using Smart Parts?

There is no foolish question, there is no final answer...

Hi, This is not the right forum to ask the question. Btw, have you checked this link: http://www.dotnetspider.com/resources/38216-Create-Excel-File-using-ASP-NET-C.aspx[^]

There is no foolish question, there is no final answer...

Download the Windows Installer Cleanup Utility setup and check if any office 2010 components are installed. If you find anything then remove it.

There is no foolish question, there is no final answer...

Naina, Check these links and hope these help: http://www.bhcblog.com/2009/10/08/sspi-handshake-failed-with-error-code-0x8009030c-while-establishing-a-connection-with-integrated-security-event-id-17806/[^] http://blog.michelbarneveld.nl/michel/archive/2009/11/11/login-failed-microsoft-sql-server-error-18452.aspx[^]

There is no foolish question, there is no final answer...

Can you check following two things? (i) Does the logged in SharePoint account have right on the database where the asp.net web part page is trying to connect? (ii) There may be space after server name in the sql connection string. Also, is your ASP.NET Web Part page running fine if you are opening it directly and without opening through WSS 3.0 page viewer web part?

There is no foolish question, there is no final answer...

Have you checked this link: http://social.msdn.microsoft.com/Forums/en/sharepointinfopath/thread/b9a57497-7006-4797-9076-3bee0e134c1e[^]

There is no foolish question, there is no final answer...

Can you please specifically tell your requirement?

There is no foolish question, there is no final answer...

If it's an OOTB workflow then try to check the sharepoint log.

There is no foolish question, there is no final answer...