ASP.NET

Mahesh.J5-Jun-08 2:22

Mahesh.J

5-Jun-08 2:22

Hi,

Thanks for your reply. Please tell me the solution.

Thanks.

ToddHileHoffer5-Jun-08 2:51

5-Jun-08 2:51

If you are using .net 2.0 or higher. I suggest using AJAX and writing server code to populate the drop down.

Do you understand why it is that if you populate a dropdown with javascript you're going to have to re-populate that list after every postback?

I didn't get any requirements for the signature

r aa j5-Jun-08 2:21

5-Jun-08 2:21

newOpt = document.createElement("OPTION");
newOpt = new Option(nodval,nodval);
libox.options.add(newOpt);

try this..

Rajendran.AL

Mahesh.J5-Jun-08 2:25

Mahesh.J

5-Jun-08 2:25

Hi,

Thanks. I have used that option only. But still after the postback the filled items gone.

r aa j5-Jun-08 2:36

5-Jun-08 2:36

send me your code

Rajendran.AL

Mahesh.J5-Jun-08 2:41

Mahesh.J

5-Jun-08 2:41

var ddlVendor = window.opener.document.getElementById(gId);

//Clears the combo box contents.
for (var count = ddlVendor.options.length-1; count >-1; count--)
{
ddlVendor.options[count] = null;
}

var vendorNodes = listNode.getElementsByTagName('Table1/Name');
var vendorIds = listNode.getElementsByTagName('Table1/Id');
var textValue;
var idValue;
var optionItem;
//Add new vendors list to the vendors combo box.
for (var count = 0; count < vendorNodes.length; count++)
{
textValue = GetInnerText(vendorNodes[count]);
idValue = GetInnerText(vendorIds[count]);
var newOption = window.opener.document.createElement('OPTION');
newOption.text = textValue;
newOption.value = idValue;
ddlVendor.options.add(newOption);
}
ddlVendor.selectedIndex = count-1;

r aa j5-Jun-08 2:49

5-Jun-08 2:49

check the for loop....length and count condition..

Rajendran.AL

need answer for transactions

Vasudevan Deepak Kumar8-Jun-08 21:10

Vasudevan Deepak Kumar

8-Jun-08 21:10

Mahesh.J wrote:
any server event

The server event resurrects the values from a statebag called ViewState. You ought to rebind your JavaScript dropdown again.

Vasudevan Deepak Kumar
Personal Homepage
Tech Gossips

All the world's a stage,
And all the men and women merely players.
They have their exits and their entrances;
And one man in his time plays many parts... --William Shakespeare

Kissy165-Jun-08 1:19

Kissy16

5-Jun-08 1:19

I have a Sub Routine as below:

Private Sub SaveRecord()
Call InsertIntoTable1
Call InsertIntoTable2
Call InsertIntoTable3
Call InsertIntoTable4
End Sub

I want to use the transaction object in such a way that it starts just before the first Insert Call and ends after the last Insert Call. The situation is that I have to save records in each table using different procedures.

Presently, if suppose records are successfully inserted in First and Second Tables and if insertion fails in Third Table then the entries done in First and Second Table must rollback.

How it can be done?

kissy

Re: need answer for transactions

ToddHileHoffer5-Jun-08 2:15

Application structure - what do you do?

5-Jun-08 2:15

http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqltransaction.aspx[^]

If you have any more questions, paste your code and I'll help you out. Its easy.

I didn't get any requirements for the signature

Rohde5-Jun-08 1:08

Rohde

5-Jun-08 1:08

So, I just listened to podcast #6 from stackoverflow.com and I was amazed when Joel Spolsky described how he structures his own ASP.NET applications. Not that there's anything wrong with it but it was just very different than how I do it.

He said that usually he has few pages and then a big switch that switches on verbs in the request address. The various case statements then makes a user control visible which then handles the actual action.

Personally I just like to have many very small pages with small responsibilities (obviously I´m mainly talking about actual web applications and not web sites) since I like it clean and lean.

Anyway this made me curious as how different people structure their ASP.NET apps. So how do you do it?

"When you have made evil the means of survival, do not expect men to remain good. Do not expect them to stay moral and lose their lives for the purpose of becoming the fodder of the immoral. Do not expect them to produce, when production is punished and looting rewarded. Do not ask, `Who is destroying the world?' You are."

-Atlas Shrugged, Ayn Rand

eyeseetee5-Jun-08 1:29

eyeseetee

5-Jun-08 1:29

Thats an interesting post but it should go in the lounge forum.

I agree with you, keep the pages clean and easy to amend or to pass on to other developers

We are not a Code Charity

N a v a n e e t h5-Jun-08 1:45

N a v a n e e t h

5-Jun-08 1:45

Rohde wrote:
I just listened to podcast #6 from stackoverflow.com

Good one. I was not aware of this. Thanks for posting Smile | :)

Rohde wrote:
Anyway this made me curious as how different people structure their ASP.NET apps. So how do you do it?

I used to consider easy maintainability while designing application. Business objects and data objects will be in separate projects. Business objects will be loosely coupled which helps to test the code easily. It also helps to improve portability and not depended with ASP.NET. I used to do dependency injection kind of design for the business objects, so that Data access objects can be easily mocked while testing.

I too create many ASPX pages. If any user interfaces are repeating in more than one page, I used to wrap it in custom controls.

All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia

How to use google | Ask smart questions

Rohde5-Jun-08 1:57

Rohde

5-Jun-08 1:57

N a v a n e e t h wrote:
Good one. I was not aware of this. Thanks for posting [Smile]

Well, basically Joel Spolsky and Jeff Atwood (from codinghorror.com) are collaborating on creating stackoverflow.com which is to be some sort of developer resource, wiki, question/answer digg-kind of thing.

And so far they have recorded 6 podcasts wherein they discuss their idea about stackoverflow and various technical programming issues as well. Pretty interesting stuff.

N a v a n e e t h wrote:
I used to consider easy maintainability while designing application. Business objects and data objects will be in separate projects. Business objects will be loosely coupled which helps to test the code easily. It also helps to improve portability and not depended with ASP.NET. I used to do dependency injection kind of design for the business objects, so that Data access objects can be easily mocked while testing.

Yeah that's pretty much as I do as well. Although I haven't used DI too much; but I'm migrating towards it.

ToddHileHoffer5-Jun-08 2:45

5-Jun-08 2:45

I know people probably won't agree with me...

But I only separate data / business rules / presentation if I know that I will need to use the code elsewhere.

I am fully aware of how to create classes that represent objects in my database. I also know how to use a generic list (of those objects) as a datasource.

That being said I often write stored procedures to be used only in one web page and just use a datareader right in the code behind. It is quicker to write, easy to debug / modify and just simpler.

I have been programming asp.net for the last 7 years and I went through a phase where I would "architect" everything. But then I found that I would end up with more bugs and have a tougher time "jumping back into the code" if a major change was requested. So now I try not to architect too much and just keep it simple.

Just my two cents. I also use lots of user controls and web pages. I try not to clutter up my aspx pages with too many controls...

I didn't get any requirements for the signature

N a v a n e e t h5-Jun-08 7:29

N a v a n e e t h

5-Jun-08 7:29

ToddHileHoffer wrote:
But then I found that I would end up with more bugs and have a tougher time "jumping back into the code" if a major change was requested. So now I try not to architect too much and just keep it simple.

I can't agree fully. AFAIK, if you have automated unit test cases, you can do this more easily. You can easily find out the areas which are breaking. Right ?

All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia

How to use google | Ask smart questions

ToddHileHoffer5-Jun-08 7:54

differentiate b/w ajax and update panel?

5-Jun-08 7:54

Well, I never did any "unit test cases".

Its not like my code was broken just the occasional object reference not set...

I didn't get any requirements for the signature

Member 38798815-Jun-08 0:23

Member 3879881

5-Jun-08 0:23

Hi i used ajax cascading dropdown for my dropdown list,
When one drop down will select based on that another dropdown will get datas...,

The same thing one of my colleague did using update panel...,
so if it will work in update panel itself then whats the need of ajax controls?,

I feel what are the things can do in ajax same efforts we can do it in update panel also...,

Then y we are going for ajax controls???...,

Plz tell me some guidens abt that...,

else forward me some good sites to differentiate those...

Thanks & Regards,
NeW OnE,
please don't forget to vote on the post

Re: differentiate b/w ajax and update panel?

r aa j5-Jun-08 0:37