G
Guest
hi all, sorry this is a bit lenghty...
I am getting stucked with an unexpected behaviour of visual studio
when I insert an sqlcommand data control in a aspx page, and
after configuring it to run a stored procedure inside MSDE I have difficulties
in getting the generated part of code from VS in place.
e.g. if I change the stored procedure inside MSDE and then try to refresh it
inside VS it does not refresh the previous generated initialization code
present
in Private Sub InitializeComponent() wich is quite annoying. For example if
I add a parameter to the procedure I cannot update that code without removing
and inserting and configuraing again a new sqlcommand in the GUI.
I thought it would just need making a refresh on Server Explorer, in
stored procedures of the connection.
Most of the times the code is not generated again unless I change the name
of the control to a never used one, and then back to original.
Sometimes my code is ok but the generated code is not there so
I get errors about missing stored procedure parameters.
Entering the code by hand to declare the parameters, is quite a bit
out of question as this replicates all over my data pages
Presently I am stuck with this cause I have to debug a submiting data page
with a big update command full of parameters.
Am I doing something wrong ?
Does this have something to do with having already a lot of SQLCommands
instatiated in a single page (about forty with stored procedures)
Is this a bug ?
I am getting stucked with an unexpected behaviour of visual studio
when I insert an sqlcommand data control in a aspx page, and
after configuring it to run a stored procedure inside MSDE I have difficulties
in getting the generated part of code from VS in place.
e.g. if I change the stored procedure inside MSDE and then try to refresh it
inside VS it does not refresh the previous generated initialization code
present
in Private Sub InitializeComponent() wich is quite annoying. For example if
I add a parameter to the procedure I cannot update that code without removing
and inserting and configuraing again a new sqlcommand in the GUI.
I thought it would just need making a refresh on Server Explorer, in
stored procedures of the connection.
Most of the times the code is not generated again unless I change the name
of the control to a never used one, and then back to original.
Sometimes my code is ok but the generated code is not there so
I get errors about missing stored procedure parameters.
Entering the code by hand to declare the parameters, is quite a bit
out of question as this replicates all over my data pages
Presently I am stuck with this cause I have to debug a submiting data page
with a big update command full of parameters.
Am I doing something wrong ?
Does this have something to do with having already a lot of SQLCommands
instatiated in a single page (about forty with stored procedures)
Is this a bug ?