|
A web control is a pretty complex object to be returned through a web service. Typically you'll only build web services that return data, the information you'll bind to the control, not the actual control.
If the web control you use is based upon the information you send through the web service, you may just want to return instructions on which web control to use, then build it on the web side.
|
|
|
|
|
Hi Developers
I decide to develop an application with C# which uses SQL server express edition.
My application shall works on the local network and some workstations use the SQL data simultaneously.
Beforehand I developed similar application with ODBC technology.
I pursue better idea, So I listen your good recommendation.Best Regards,
Reza Shojaee
|
|
|
|
|
|
You can use sqlconnection for local client and odbcconnection for remote client Best Regards,
Reza Shojaee
|
|
|
|
|
Depends how big your project is but it is worth Looking up LINQ to Entities and NHibernate. These are both ORM frameworks that allow you have a relational database, whilst living in the object world on the C# side. After this, LINQ to SQL is a possible, lighter weight choice. Finally you could use straight ADO, but in a good implementation this alone can be cumbersome.
NHibernate currently has better features, but long-term LINQ Entities might be the pony to back, as the framework is by Microsoft, and comes with .NET 3.5 as standard.Cpianism: I have a negative number in my Rep so please fix it.
Chris Maunder: That isn't a bug.
|
|
|
|
|
Hi My friend
My project isn't very big, But I like new experiences.
Beforehand I heard about LINQ but NHibernate is unfamiliar technology for me.
My project is a windows application, these technologies only use for web or no?
Do you know good example of these technologies ? Best Regards,
Reza Shojaee
|
|
|
|
|
Reza Shojaee wrote: My project is a windows application, these technologies only use for web or no
These technologies are intended to allow .net applications (of whatever type) to communicate with the database. As long as you can connect to the database across your network, they should be fine.
Reza Shojaee wrote: Do you know good example of these technologies
I suggest either doing a search on this site (I'm sure there are some excellent articles around), or googling for them. I started using these a while back, so I haven't looked at introductory articles in a while.Cpianism: I have a negative number in my Rep so please fix it.
Chris Maunder: That isn't a bug.
|
|
|
|
|
|
|
|
|
Nematjon Rahmanov wrote: Please stop chating in arabianFarsi
They've been reported, when the hamsters wake up, doubtlessly they'll be banned.Cpianism: I have a negative number in my Rep so please fix it.
Chris Maunder: That isn't a bug.
|
|
|
|
|
Let us hope so. btw are you aware of this[^]? MVP 2010 - are they mad?
|
|
|
|
|
Richard MacCutchan wrote: btw are you aware of this[^]?
Yes, thanks, I'm just rising above it.Cpianism: I have a negative number in my Rep so please fix it.
Chris Maunder: That isn't a bug.
|
|
|
|
|
|
|
روي صفحه كليك ميكنم پيغام ميده
please dont steal my stuff!!!!
|
|
|
|
|
|
|
|
گلم امروز نميتونم ببينم فردا ميام حتما ميبينم
|
|
|
|
|
|
Good day.
I have a problem with shell context menu register on x64 pc.
My shell extension working well on 32 bit, but in 64 bit not working.
I search google ,msdn , but can't find answer.Please help me.
My code parts :
<br />
Assembly executingAssembly = Assembly.GetExecutingAssembly();<br />
RegistrationServices services = new RegistrationServices();<br />
services.RegisterAssembly(executingAssembly, AssemblyRegistrationFlags.SetCodeBase);<br />
<br />
.................<br />
<br />
RegistryKey key2 = Registry.CurrentUser.OpenSubKey(@"Software\Microsoft\Windows\CurrentVersion\Explorer", true);<br />
key2.SetValue("DesktopProcess", 1);<br />
key2.Close();<br />
key2 = Registry.LocalMachine.OpenSubKey(@"Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved", true);<br />
key2.SetValue(myguid, mytext);<br />
key2.Close();<br />
<br />
key2 = Registry.ClassesRoot.CreateSubKey(@"Drive\shellex\ContextMenuHandlers\"+mytext);<br />
key2.SetValue("", myguid);<br />
key2.Close();<br />
Thanks for reply.
Nematjon.
|
|
|
|
|
Shell extensions get loaded into every process with a file open dialog; but there can be only one .NET runtime per process.
Shell extensions written in .NET are dangerous: they can break applications using other versions of .NET.
Read this post for more details: http://social.msdn.microsoft.com/forums/en-US/netfxbcl/thread/1428326d-7950-42b4-ad94-8e962124043e/[^]
Do not write shell extensions in .NET unless you are 100% sure that none of your users use any .NET 1.x applications.
For your x64 problem: are you aware that 32-bit and 64-bit processes have separate registries? Make sure your registration process is running as 64-bit process so that it writes to the same registry that explorer is reading from.
|
|
|
|
|
Thanks for your reply Daniel .
Yes , i know 32 bit app and 64 app registration different place.
I rebuild my app under x64.I check registry and they are i found my settings.
But not yet working shell menu .
I'm using Vista 32 bit , Visual Studio 2008.
Testing pc is Windows 7 , 64 bit.
Please help me this issue .
Thanks.
Nematjon.good
modified on Monday, February 8, 2010 9:08 AM
|
|
|
|