This blog is about my history as a software engineer utilizing technologies C#, Java, React, JavaScript, .NET Core, SQL Server , Oracle, GIT, GitHub, Jira, Azure, AWS and HTML5. “I have not failed. I've just found 10,000 ways that won't work.” Thomas A. Edison. Please click on all my ADVERTISING links to help support this blog. Thank you.
Tuesday, May 30, 2006
Update to Access Folders without reboot
Need to access a folder you were just given access to? No need to reboot. Simply go to Start > Run > Type CMD At the dos prompt type gpupdate
Friday, May 19, 2006
SQL Server Leading Zeros for CHAR Type
declare @DirectiveNumber char(6)
declare @DirLength int
SET @DirectiveNumber = (SELECT DirectiveNumber FROM dbo.tblPlants WHERE PlantId = '1201')
--UPDATE dbo.tblPlants SET DirectiveNumber =
SET @DirectiveNumber = @DirectiveNumber + 1
Select @DirLength = LEN(@DirectiveNumber)
IF (@DirLength = 1)
SET @DirectiveNumber = '00000' + @DirectiveNumber
IF (@DirLength = 2)
SET @DirectiveNumber = '0000' + @DirectiveNumber
IF (@DirLength = 3)
SET @DirectiveNumber = '000' + @DirectiveNumber
IF (@DirLength = 4)
SET @DirectiveNumber = '00' + @DirectiveNumber
IF (@DirLength = 5)
SET @DirectiveNumber = '0' + @DirectiveNumber
UPDATE dbo.tblPlants SET DirectiveNumber = @DirectiveNumber WHERE PlantId = '1201'
SELECT @DirectiveNumber
declare @DirLength int
SET @DirectiveNumber = (SELECT DirectiveNumber FROM dbo.tblPlants WHERE PlantId = '1201')
--UPDATE dbo.tblPlants SET DirectiveNumber =
SET @DirectiveNumber = @DirectiveNumber + 1
Select @DirLength = LEN(@DirectiveNumber)
IF (@DirLength = 1)
SET @DirectiveNumber = '00000' + @DirectiveNumber
IF (@DirLength = 2)
SET @DirectiveNumber = '0000' + @DirectiveNumber
IF (@DirLength = 3)
SET @DirectiveNumber = '000' + @DirectiveNumber
IF (@DirLength = 4)
SET @DirectiveNumber = '00' + @DirectiveNumber
IF (@DirLength = 5)
SET @DirectiveNumber = '0' + @DirectiveNumber
UPDATE dbo.tblPlants SET DirectiveNumber = @DirectiveNumber WHERE PlantId = '1201'
SELECT @DirectiveNumber
Tuesday, May 16, 2006
ASP.NET 2.0
WOW,
Well I just deployed my first ASP.NET 2.0. What a difference from 1.x.
I learned that you can deploy by using a publish and precompiled mode that will not cause a slow load the first time a user accesses the site, but the issue with using that is that when you make change you have to redeploy all the .aspx and .dll files again. That kinda sucks.
However, after a little research I found a tool that add-ons from microsoft: http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/
This feature more reflects the ASP.NET 1.x way of creating dlls
Well I just deployed my first ASP.NET 2.0. What a difference from 1.x.
I learned that you can deploy by using a publish and precompiled mode that will not cause a slow load the first time a user accesses the site, but the issue with using that is that when you make change you have to redeploy all the .aspx and .dll files again. That kinda sucks.
However, after a little research I found a tool that add-ons from microsoft: http://msdn.microsoft.com/asp.net/reference/infrastructure/wdp/
This feature more reflects the ASP.NET 1.x way of creating dlls
Friday, May 12, 2006
How do I hide a column in my Datagrid if AutoGenerateColumns is set to True?
Question: How do I hide a column in my Datagrid if AutoGenerateColumns is set to True?
Answer: AutoGenerated columns do not appear in the Datagrid's Columns() collection, and so the usual method of hiding a Datagrid column will fail:
'Will NOT work for AutoGenerated columns:
Datagrid1.Columns(1).Visible = False
So the place to handle this is in the ItemDataBound event of the Datagrid:
<asp:DataGrid id="Datagrid1" runat="server" AutoGenerateColumns="True" OnItemDataBound="Datagrid1_OnItemDataBound"/>
Codebehind
Private Sub Datagrid1_OnItemDataBound(s As Object, e As DatagridItemEventArgs)
e.Item.Cells(1).Visible = False
End Sub
Answer: AutoGenerated columns do not appear in the Datagrid's Columns() collection, and so the usual method of hiding a Datagrid column will fail:
'Will NOT work for AutoGenerated columns:
Datagrid1.Columns(1).Visible = False
So the place to handle this is in the ItemDataBound event of the Datagrid:
<asp:DataGrid id="Datagrid1" runat="server" AutoGenerateColumns="True" OnItemDataBound="Datagrid1_OnItemDataBound"/>
Codebehind
Private Sub Datagrid1_OnItemDataBound(s As Object, e As DatagridItemEventArgs)
e.Item.Cells(1).Visible = False
End Sub
Tuesday, May 09, 2006
Monday, May 08, 2006
Parse Error When adding new Web pages to application
I am banging my head on this one... All of my other Web forms work fine but now...
I am getting the following error when adding new Web forms to my application:
I just added simple Web form with Hello World typed on the page.
Server Error in '/XXX.QuipSap.WebUi' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'XXX.QuipSap.WebUi.TestForm'.
Source Error:
Line 1: <%@ Page Language="vb" AutoEventWireup="false" Codebehind="TestForm.aspx.vb" Inherits="XXX.QuipSap.WebUi.TestForm"%>
Line 2:
Line 3:
Source File: c:\inetpub\wwwroot\XXX.QuipSap.WebUi\TestForm.aspx Line: 1
SOLUTION:
OK as crazy as a solution that this sounds, but I am not to happy with the solution but it works.
When I create add a new Web form I just remove the inherits part from the first line of the aspx page. If I add labels or buttons and double click on them VS.NET 2003 adds back the inherits and magically (HMM I say magically because if I knew what was fixing it I would not be writting this) fixes the issue.
I am getting the following error when adding new Web forms to my application:
I just added simple Web form with Hello World typed on the page.
Server Error in '/XXX.QuipSap.WebUi' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'XXX.QuipSap.WebUi.TestForm'.
Source Error:
Line 1: <%@ Page Language="vb" AutoEventWireup="false" Codebehind="TestForm.aspx.vb" Inherits="XXX.QuipSap.WebUi.TestForm"%>
Line 2:
Line 3:
Source File: c:\inetpub\wwwroot\XXX.QuipSap.WebUi\TestForm.aspx Line: 1
SOLUTION:
OK as crazy as a solution that this sounds, but I am not to happy with the solution but it works.
When I create add a new Web form I just remove the inherits part from the first line of the aspx page. If I add labels or buttons and double click on them VS.NET 2003 adds back the inherits and magically (HMM I say magically because if I knew what was fixing it I would not be writting this) fixes the issue.
Parse Error When adding new Web pages to application
I am banging my head on this one... All of my other Web forms work fine but now...
I am getting the following error when adding new Web forms to my application:
I just added simple Web form with Hello World typed on the page.
Server Error in '/XXX.QuipSap.WebUi' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'XXX.QuipSap.WebUi.TestForm'.
Source Error:
Line 1: <%@ Page Language="vb" AutoEventWireup="false" Codebehind="TestForm.aspx.vb" Inherits="XXX.QuipSap.WebUi.TestForm"%>
Line 2:
Line 3:
Source File: c:\inetpub\wwwroot\XXX.QuipSap.WebUi\TestForm.aspx Line: 1
SOLUTION:
OK as crazy as a solution that this sounds, but I am not to happy with the solution but it works.
When I create add a new Web form I just remove the inherits part from the first line of the aspx page. If I add labels or buttons and double click on them VS.NET 2003 adds back the inherits and magically (HMM I say magically because if I knew what was fixing it I would not be writting this) fixes the issue.
I am getting the following error when adding new Web forms to my application:
I just added simple Web form with Hello World typed on the page.
Server Error in '/XXX.QuipSap.WebUi' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'XXX.QuipSap.WebUi.TestForm'.
Source Error:
Line 1: <%@ Page Language="vb" AutoEventWireup="false" Codebehind="TestForm.aspx.vb" Inherits="XXX.QuipSap.WebUi.TestForm"%>
Line 2:
Line 3:
Source File: c:\inetpub\wwwroot\XXX.QuipSap.WebUi\TestForm.aspx Line: 1
SOLUTION:
OK as crazy as a solution that this sounds, but I am not to happy with the solution but it works.
When I create add a new Web form I just remove the inherits part from the first line of the aspx page. If I add labels or buttons and double click on them VS.NET 2003 adds back the inherits and magically (HMM I say magically because if I knew what was fixing it I would not be writting this) fixes the issue.
Parse Error When adding new Web pages to application
I am banging my head on this one... All of my other Web forms work fine but now...
I am getting the following error when adding new Web forms to my application:
I just added simple Web form with Hello World typed on the page.
Server Error in '/XXX.QuipSap.WebUi' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'XXX.QuipSap.WebUi.TestForm'.
Source Error:
Line 1: <%@ Page Language="vb" AutoEventWireup="false" Codebehind="TestForm.aspx.vb" Inherits="XXX.QuipSap.WebUi.TestForm"%>
Line 2:
Line 3:
Source File: c:\inetpub\wwwroot\XXX.QuipSap.WebUi\TestForm.aspx Line: 1
SOLUTION:
OK as crazy as a solution that this sounds, but I am not to happy with the solution but it works.
When I create add a new Web form I just remove the inherits part from the first line of the aspx page. If I add labels or buttons and double click on them VS.NET 2003 adds back the inherits and magically (HMM I say magically because if I knew what was fixing it I would not be writting this) fixes the issue.
I am getting the following error when adding new Web forms to my application:
I just added simple Web form with Hello World typed on the page.
Server Error in '/XXX.QuipSap.WebUi' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'XXX.QuipSap.WebUi.TestForm'.
Source Error:
Line 1: <%@ Page Language="vb" AutoEventWireup="false" Codebehind="TestForm.aspx.vb" Inherits="XXX.QuipSap.WebUi.TestForm"%>
Line 2:
Line 3:
Source File: c:\inetpub\wwwroot\XXX.QuipSap.WebUi\TestForm.aspx Line: 1
SOLUTION:
OK as crazy as a solution that this sounds, but I am not to happy with the solution but it works.
When I create add a new Web form I just remove the inherits part from the first line of the aspx page. If I add labels or buttons and double click on them VS.NET 2003 adds back the inherits and magically (HMM I say magically because if I knew what was fixing it I would not be writting this) fixes the issue.
Parse Error When adding new Web pages to application
I am banging my head on this one... All of my other Web forms work fine but now...
I am getting the following error when adding new Web forms to my application:
I just added simple Web form with Hello World typed on the page.
Server Error in '/XXX.QuipSap.WebUi' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'XXX.QuipSap.WebUi.TestForm'.
Source Error:
Line 1: <%@ Page Language="vb" AutoEventWireup="false" Codebehind="TestForm.aspx.vb" Inherits="XXX.QuipSap.WebUi.TestForm"%>
Line 2:
Line 3:
Source File: c:\inetpub\wwwroot\XXX.QuipSap.WebUi\TestForm.aspx Line: 1
SOLUTION:
OK as crazy as a solution that this sounds, but I am not to happy with the solution but it works.
When I create add a new Web form I just remove the inherits part from the first line of the aspx page. If I add labels or buttons and double click on them VS.NET 2003 adds back the inherits and magically (HMM I say magically because if I knew what was fixing it I would not be writting this) fixes the issue.
I am getting the following error when adding new Web forms to my application:
I just added simple Web form with Hello World typed on the page.
Server Error in '/XXX.QuipSap.WebUi' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'XXX.QuipSap.WebUi.TestForm'.
Source Error:
Line 1: <%@ Page Language="vb" AutoEventWireup="false" Codebehind="TestForm.aspx.vb" Inherits="XXX.QuipSap.WebUi.TestForm"%>
Line 2:
Line 3:
Source File: c:\inetpub\wwwroot\XXX.QuipSap.WebUi\TestForm.aspx Line: 1
SOLUTION:
OK as crazy as a solution that this sounds, but I am not to happy with the solution but it works.
When I create add a new Web form I just remove the inherits part from the first line of the aspx page. If I add labels or buttons and double click on them VS.NET 2003 adds back the inherits and magically (HMM I say magically because if I knew what was fixing it I would not be writting this) fixes the issue.
Subscribe to:
Posts (Atom)