Worksheet Names Cannot be more than 31 Characters c#

-
 
         Hi, Today I am Facing This Issue In My Project. When We Write Excel Sheet C# Via. In Excel, SheetName Allows Only 31 Characters. Otherwise, You Can Write More then 31 Characters You Will Faced This Issue.

         I Am using Closed XML  for Write Excel Sheet. To Rectify this issue to Write Following Code. You can Write The SheetName.


    using (XLWorkbook wb = new XLWorkbook())
                {
                    wb.Worksheets.Add(dt,"Sheetname");




Comments

Post a Comment

Thank You for your Comment

Popular posts from this blog

Unable to perform operation on the item is locked in workspace

-
Image
Hi,  I am getting this issue last week. so I Fixed. I Will share the Solution. Some files struggle with another person's systems workspace. then you can't able to check-in in your TFS. The particular file was blocked or Locked in another person system so easily remove that person Workspace issue will be solved you can check-in your file into the TFS. tf workspace /delete /server:http://192.168.1.50:8080/tfs/projectname NCS-P01-001_2;R****h
Read more

Maximum Stored Procedure Function Trigger or View Nesting Level Exceeded (limit 32) in SQL Server

-
Image
                  In SQL Server I am facing some error on when it Runs Procedure. That as Maximum Stored Procedure Function Trigger or View Nesting Level Exceeded (limit 32) in SQL Server. Reason:                       user-defined function begins execution and decreases by one when the called stored procedure, managed code reference, or user-defined function completes execution. Attempting to exceed the maximum of 32 levels of nesting causes the whole calling chain to fail and for this error message to be raised.   Solution: To Run this code in Your SQL SERVER Avoid In this Error. SP_CONFIGURE 'nested_triggers' ,0 GO RECONFIGURE GO
Read more

Insecure cookie setting: missing Secure flag

-
  Issue Description: Insecure Cookie Setting - Missing Secure Flag Explanation: The "Secure" flag is an attribute that can be set for cookies in web applications. When the Secure flag is enabled for a cookie, the cookie is only transmitted over HTTPS connections, ensuring that it is sent securely over an encrypted channel. This is crucial for security because it helps prevent the exposure of sensitive information contained in cookies, such as session tokens or authentication credentials, to potential attackers. When the Secure flag is missing from a cookie, it means that the cookie can be sent over both secure (HTTPS) and non-secure (HTTP) connections. This can pose a significant security risk, as sensitive information could be exposed if the cookie is transmitted over an insecure connection. Impact: The impact of missing the Secure flag on a cookie depends on the context in which the cookie is used. Here are some potential risks: Session Hijacking: If an attacker can inter...
Read more