Hi All,
I've got a problem where my application loads an assembly in the running
AppDomain when it shouldn't.
Ok, I've got a RemotingHost application that configs the remoting stuff and
then...
asks the user for a list of .net DLLs.
the app then copies a these assemblies to a cache folder along with my
RemotingClient app. Once copies i config a AppDomain setup and create a new
AppDomain.
Once created, i loop through the user chosen assemblies and load into the
AppDomain. I then AppDomain.ExecuteAssembly my RemotingClient.
The purpose is so that I can dynamically load and unload assemblies and
report on type information to my main app (in this case the RemotingHost).
Everything works fine in principal, however when I load the DLLs from my
cache folder the assembly is actually loaded in both AppDomains.
I know if i reference a type across AppDomain, it will cause the Framework
to load the assembly in the other AppDomain, but all i'm doing it is loading
it?
Any ideas? (please help:)
TIA
Sam Martin
(code sample below)
System.IO.Directory.CreateDirectory(Application.St artupPath+"\\cache");
// copy my RemotingClient.exe to the cache
// Set up the AppDomainSetup
AppDomainSetup setup = new AppDomainSetup();
setup.ApplicationBase = Application.StartupPath+"\\cache\\";
setup.ConfigurationFile = "";
// Set up the Evidence
System.Security.Policy.Evidence baseEvidence =
AppDomain.CurrentDomain.Evidence;
System.Security.Policy.Evidence evidence = new
System.Security.Policy.Evidence(baseEvidence);
// evidence.AddAssembly("(some assembly)");
// Create the AppDomain
AppDomain newDomain = AppDomain.CreateDomain("temp", evidence, setup);
foreach(string an in this.listBoxAsmList.Items)
{
// copy the specified assembly to cache
string asmn = an.ToLower().Replace(".dll","");
asmn = MyFuncToGetAsmDisplayName(an);
newDomain.Load(asmn);
}
newDomain.ExecuteAssembly("RemotingClient.exe);
AppDomain.Unload(newDomain); 5 7376
If you're loading the assemblies using AppDomain.Load(), that function
returns an Assembly object to the AppDomain of the caller, which causes the
caller to load the assembly as well. Read the "remarks" section of the
following documentation: http://msdn.microsoft.com/library/en...asp?frame=true
One way to force an assembly to be loaded into another AppDomain without it
being loaded into the current one is to use the AppDomain.DoCallback()
method to invoke a delegate that will run in the AppDomain in which you want
the assembly loaded. For example,
class Class1
{
[STAThread]
static void Main(string[] args)
{
AppDomainSetup s = new AppDomainSetup();
s.ApplicationBase =
AppDomain.CurrentDomain.SetupInformation.Applicati onBase;
AppDomain d = AppDomain.CreateDomain("TestDomain",
AppDomain.CurrentDomain.Evidence, s);
d.DoCallBack(new CrossAppDomainDelegate(DomainCall));
// ...
}
public static void DomainCall()
{
AppDomain.CurrentDomain.Load("MyAssembly");
}
}
The main thing to make sure of is that your delegate does not reference an
instance method of a MarshalByRef object, or else the assembly will be
loaded in the domain in which that object resides.
Hope that helps -
Ken
"Sam Martin" <sa*********@yahoo.co.uk> wrote in message
news:eq*************@TK2MSFTNGP09.phx.gbl... Hi All,
I've got a problem where my application loads an assembly in the running AppDomain when it shouldn't.
Ok, I've got a RemotingHost application that configs the remoting stuff
and then... asks the user for a list of .net DLLs. the app then copies a these assemblies to a cache folder along with my RemotingClient app. Once copies i config a AppDomain setup and create a
new AppDomain. Once created, i loop through the user chosen assemblies and load into the AppDomain. I then AppDomain.ExecuteAssembly my RemotingClient.
The purpose is so that I can dynamically load and unload assemblies and report on type information to my main app (in this case the RemotingHost). Everything works fine in principal, however when I load the DLLs from my cache folder the assembly is actually loaded in both AppDomains.
I know if i reference a type across AppDomain, it will cause the Framework to load the assembly in the other AppDomain, but all i'm doing it is
loading it?
Any ideas? (please help:)
TIA Sam Martin
(code sample below)
System.IO.Directory.CreateDirectory(Application.St artupPath+"\\cache");
// copy my RemotingClient.exe to the cache
// Set up the AppDomainSetup AppDomainSetup setup = new AppDomainSetup(); setup.ApplicationBase = Application.StartupPath+"\\cache\\"; setup.ConfigurationFile = "";
// Set up the Evidence System.Security.Policy.Evidence baseEvidence = AppDomain.CurrentDomain.Evidence; System.Security.Policy.Evidence evidence = new System.Security.Policy.Evidence(baseEvidence); // evidence.AddAssembly("(some assembly)");
// Create the AppDomain AppDomain newDomain = AppDomain.CreateDomain("temp", evidence, setup);
foreach(string an in this.listBoxAsmList.Items) {
// copy the specified assembly to cache
string asmn = an.ToLower().Replace(".dll","");
asmn = MyFuncToGetAsmDisplayName(an); newDomain.Load(asmn); }
newDomain.ExecuteAssembly("RemotingClient.exe); AppDomain.Unload(newDomain);
it all becomes clear.
thanks mate
"Ken Kolda" <ke*******@elliemae-nospamplease.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl... If you're loading the assemblies using AppDomain.Load(), that function returns an Assembly object to the AppDomain of the caller, which causes
the caller to load the assembly as well. Read the "remarks" section of the following documentation:
http://msdn.microsoft.com/library/en...asp?frame=true One way to force an assembly to be loaded into another AppDomain without
it being loaded into the current one is to use the AppDomain.DoCallback() method to invoke a delegate that will run in the AppDomain in which you
want the assembly loaded. For example,
class Class1 { [STAThread] static void Main(string[] args) { AppDomainSetup s = new AppDomainSetup(); s.ApplicationBase = AppDomain.CurrentDomain.SetupInformation.Applicati onBase; AppDomain d = AppDomain.CreateDomain("TestDomain", AppDomain.CurrentDomain.Evidence, s);
d.DoCallBack(new CrossAppDomainDelegate(DomainCall)); // ... }
public static void DomainCall() { AppDomain.CurrentDomain.Load("MyAssembly"); } }
The main thing to make sure of is that your delegate does not reference an instance method of a MarshalByRef object, or else the assembly will be loaded in the domain in which that object resides.
Hope that helps - Ken "Sam Martin" <sa*********@yahoo.co.uk> wrote in message news:eq*************@TK2MSFTNGP09.phx.gbl... Hi All,
I've got a problem where my application loads an assembly in the running AppDomain when it shouldn't.
Ok, I've got a RemotingHost application that configs the remoting stuff and then... asks the user for a list of .net DLLs. the app then copies a these assemblies to a cache folder along with my RemotingClient app. Once copies i config a AppDomain setup and create a new AppDomain. Once created, i loop through the user chosen assemblies and load into
the AppDomain. I then AppDomain.ExecuteAssembly my RemotingClient.
The purpose is so that I can dynamically load and unload assemblies and report on type information to my main app (in this case the
RemotingHost). Everything works fine in principal, however when I load the DLLs from my cache folder the assembly is actually loaded in both AppDomains.
I know if i reference a type across AppDomain, it will cause the
Framework to load the assembly in the other AppDomain, but all i'm doing it is loading it?
Any ideas? (please help:)
TIA Sam Martin
(code sample below)
System.IO.Directory.CreateDirectory(Application.St artupPath+"\\cache");
// copy my RemotingClient.exe to the cache
// Set up the AppDomainSetup AppDomainSetup setup = new AppDomainSetup(); setup.ApplicationBase = Application.StartupPath+"\\cache\\"; setup.ConfigurationFile = "";
// Set up the Evidence System.Security.Policy.Evidence baseEvidence = AppDomain.CurrentDomain.Evidence; System.Security.Policy.Evidence evidence = new System.Security.Policy.Evidence(baseEvidence); // evidence.AddAssembly("(some assembly)");
// Create the AppDomain AppDomain newDomain = AppDomain.CreateDomain("temp", evidence,
setup); foreach(string an in this.listBoxAsmList.Items) {
// copy the specified assembly to cache
string asmn = an.ToLower().Replace(".dll","");
asmn = MyFuncToGetAsmDisplayName(an); newDomain.Load(asmn); }
newDomain.ExecuteAssembly("RemotingClient.exe); AppDomain.Unload(newDomain);
ahh, one other thing. how would i specify which assembly to load from the
main appdomain
I could do something like, but even if libraryName is a static property of a
class in the main AppDomain, it's value would be null in the other AppDomain
public static void DomainCall()
{
AppDomain.CurrentDomain.Load(libraryName);
}
you see what i mean, i need to say which assembly to load into the AppDomain
from the calling AppDomain without loading the spec'd assembly.
TIA
Sam Martin
"Ken Kolda" <ke*******@elliemae-nospamplease.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl... If you're loading the assemblies using AppDomain.Load(), that function returns an Assembly object to the AppDomain of the caller, which causes
the caller to load the assembly as well. Read the "remarks" section of the following documentation:
http://msdn.microsoft.com/library/en...asp?frame=true One way to force an assembly to be loaded into another AppDomain without
it being loaded into the current one is to use the AppDomain.DoCallback() method to invoke a delegate that will run in the AppDomain in which you
want the assembly loaded. For example,
class Class1 { [STAThread] static void Main(string[] args) { AppDomainSetup s = new AppDomainSetup(); s.ApplicationBase = AppDomain.CurrentDomain.SetupInformation.Applicati onBase; AppDomain d = AppDomain.CreateDomain("TestDomain", AppDomain.CurrentDomain.Evidence, s);
d.DoCallBack(new CrossAppDomainDelegate(DomainCall)); // ... }
public static void DomainCall() { AppDomain.CurrentDomain.Load("MyAssembly"); } }
The main thing to make sure of is that your delegate does not reference an instance method of a MarshalByRef object, or else the assembly will be loaded in the domain in which that object resides.
Hope that helps - Ken "Sam Martin" <sa*********@yahoo.co.uk> wrote in message news:eq*************@TK2MSFTNGP09.phx.gbl... Hi All,
I've got a problem where my application loads an assembly in the running AppDomain when it shouldn't.
Ok, I've got a RemotingHost application that configs the remoting stuff and then... asks the user for a list of .net DLLs. the app then copies a these assemblies to a cache folder along with my RemotingClient app. Once copies i config a AppDomain setup and create a new AppDomain. Once created, i loop through the user chosen assemblies and load into
the AppDomain. I then AppDomain.ExecuteAssembly my RemotingClient.
The purpose is so that I can dynamically load and unload assemblies and report on type information to my main app (in this case the
RemotingHost). Everything works fine in principal, however when I load the DLLs from my cache folder the assembly is actually loaded in both AppDomains.
I know if i reference a type across AppDomain, it will cause the
Framework to load the assembly in the other AppDomain, but all i'm doing it is loading it?
Any ideas? (please help:)
TIA Sam Martin
(code sample below)
System.IO.Directory.CreateDirectory(Application.St artupPath+"\\cache");
// copy my RemotingClient.exe to the cache
// Set up the AppDomainSetup AppDomainSetup setup = new AppDomainSetup(); setup.ApplicationBase = Application.StartupPath+"\\cache\\"; setup.ConfigurationFile = "";
// Set up the Evidence System.Security.Policy.Evidence baseEvidence = AppDomain.CurrentDomain.Evidence; System.Security.Policy.Evidence evidence = new System.Security.Policy.Evidence(baseEvidence); // evidence.AddAssembly("(some assembly)");
// Create the AppDomain AppDomain newDomain = AppDomain.CreateDomain("temp", evidence,
setup); foreach(string an in this.listBoxAsmList.Items) {
// copy the specified assembly to cache
string asmn = an.ToLower().Replace(".dll","");
asmn = MyFuncToGetAsmDisplayName(an); newDomain.Load(asmn); }
newDomain.ExecuteAssembly("RemotingClient.exe); AppDomain.Unload(newDomain);
In this case, you probably want to do something a bit more sophisticated
using remoting. What I would do is create a class such as:
class AssemblyLoader : MarshalByRefObject
{
public void Load(string assemblyName)
{
AppDomain.CurrentDomain.Load(assemblyName);
}
}
Then, from your main app domain, create an instance of this class in the new
app domain, e.g.
AssemblyLoader loader =
(AssemblyLoader) newDomain.CreateInstanceAndUnwrap("MyAssembly",
"MyAssembly.AssemblyLoader");
loader.Load("PluginAssembly");
The disadvantage of this technique is that your new AppDomain will have to
load the current assembly to get the definition of the AssemblyLoader class.
Hope that helps -
Ken
"Sam Martin" <sa*********@yahoo.co.uk> wrote in message
news:%2***************@tk2msftngp13.phx.gbl... ahh, one other thing. how would i specify which assembly to load from the main appdomain I could do something like, but even if libraryName is a static property of
a class in the main AppDomain, it's value would be null in the other
AppDomain public static void DomainCall() { AppDomain.CurrentDomain.Load(libraryName); }
you see what i mean, i need to say which assembly to load into the
AppDomain from the calling AppDomain without loading the spec'd assembly.
TIA
Sam Martin
"Ken Kolda" <ke*******@elliemae-nospamplease.com> wrote in message news:%2****************@tk2msftngp13.phx.gbl... If you're loading the assemblies using AppDomain.Load(), that function returns an Assembly object to the AppDomain of the caller, which causes the caller to load the assembly as well. Read the "remarks" section of the following documentation:
http://msdn.microsoft.com/library/en...asp?frame=true One way to force an assembly to be loaded into another AppDomain without
it being loaded into the current one is to use the AppDomain.DoCallback() method to invoke a delegate that will run in the AppDomain in which you want the assembly loaded. For example,
class Class1 { [STAThread] static void Main(string[] args) { AppDomainSetup s = new AppDomainSetup(); s.ApplicationBase = AppDomain.CurrentDomain.SetupInformation.Applicati onBase; AppDomain d = AppDomain.CreateDomain("TestDomain", AppDomain.CurrentDomain.Evidence, s);
d.DoCallBack(new CrossAppDomainDelegate(DomainCall)); // ... }
public static void DomainCall() { AppDomain.CurrentDomain.Load("MyAssembly"); } }
The main thing to make sure of is that your delegate does not reference
an instance method of a MarshalByRef object, or else the assembly will be loaded in the domain in which that object resides.
Hope that helps - Ken "Sam Martin" <sa*********@yahoo.co.uk> wrote in message news:eq*************@TK2MSFTNGP09.phx.gbl... Hi All,
I've got a problem where my application loads an assembly in the
running AppDomain when it shouldn't.
Ok, I've got a RemotingHost application that configs the remoting
stuff and then... asks the user for a list of .net DLLs. the app then copies a these assemblies to a cache folder along with my RemotingClient app. Once copies i config a AppDomain setup and create
a new AppDomain. Once created, i loop through the user chosen assemblies and load into the AppDomain. I then AppDomain.ExecuteAssembly my RemotingClient.
The purpose is so that I can dynamically load and unload assemblies
and report on type information to my main app (in this case the RemotingHost). Everything works fine in principal, however when I load the DLLs from
my cache folder the assembly is actually loaded in both AppDomains.
I know if i reference a type across AppDomain, it will cause the Framework to load the assembly in the other AppDomain, but all i'm doing it is
loading it?
Any ideas? (please help:)
TIA Sam Martin
(code sample below)
System.IO.Directory.CreateDirectory(Application.St artupPath+"\\cache"); // copy my RemotingClient.exe to the cache
// Set up the AppDomainSetup AppDomainSetup setup = new AppDomainSetup(); setup.ApplicationBase = Application.StartupPath+"\\cache\\"; setup.ConfigurationFile = "";
// Set up the Evidence System.Security.Policy.Evidence baseEvidence = AppDomain.CurrentDomain.Evidence; System.Security.Policy.Evidence evidence = new System.Security.Policy.Evidence(baseEvidence); // evidence.AddAssembly("(some assembly)");
// Create the AppDomain AppDomain newDomain = AppDomain.CreateDomain("temp", evidence, setup); foreach(string an in this.listBoxAsmList.Items) {
// copy the specified assembly to cache
string asmn = an.ToLower().Replace(".dll","");
asmn = MyFuncToGetAsmDisplayName(an); newDomain.Load(asmn); }
newDomain.ExecuteAssembly("RemotingClient.exe); AppDomain.Unload(newDomain);
yeah it does unfortunately.
almost had that working, but found the host (the assembly loader) kept being
loaded too - which i don't want really. otherwise i could have just loaded
everything together in a single appdomain using another appdomain to
effectively restart the app when i wanted to use a dif set of libraries.
shit, & all because you cannot unload an assembly from an appdomain.
thanks anyway
sam
"Ken Kolda" <ke*******@elliemae-nospamplease.com> wrote in message
news:eh**************@TK2MSFTNGP11.phx.gbl... In this case, you probably want to do something a bit more sophisticated using remoting. What I would do is create a class such as:
class AssemblyLoader : MarshalByRefObject { public void Load(string assemblyName) { AppDomain.CurrentDomain.Load(assemblyName); } }
Then, from your main app domain, create an instance of this class in the
new app domain, e.g.
AssemblyLoader loader = (AssemblyLoader) newDomain.CreateInstanceAndUnwrap("MyAssembly", "MyAssembly.AssemblyLoader"); loader.Load("PluginAssembly");
The disadvantage of this technique is that your new AppDomain will have to load the current assembly to get the definition of the AssemblyLoader
class. Hope that helps - Ken
"Sam Martin" <sa*********@yahoo.co.uk> wrote in message news:%2***************@tk2msftngp13.phx.gbl... ahh, one other thing. how would i specify which assembly to load from
the main appdomain I could do something like, but even if libraryName is a static property
of a class in the main AppDomain, it's value would be null in the other AppDomain public static void DomainCall() { AppDomain.CurrentDomain.Load(libraryName); }
you see what i mean, i need to say which assembly to load into the
AppDomain from the calling AppDomain without loading the spec'd assembly.
TIA
Sam Martin
"Ken Kolda" <ke*******@elliemae-nospamplease.com> wrote in message news:%2****************@tk2msftngp13.phx.gbl... If you're loading the assemblies using AppDomain.Load(), that function returns an Assembly object to the AppDomain of the caller, which
causes the caller to load the assembly as well. Read the "remarks" section of the following documentation:
http://msdn.microsoft.com/library/en...asp?frame=true One way to force an assembly to be loaded into another AppDomain
without it being loaded into the current one is to use the AppDomain.DoCallback() method to invoke a delegate that will run in the AppDomain in which
you want the assembly loaded. For example,
class Class1 { [STAThread] static void Main(string[] args) { AppDomainSetup s = new AppDomainSetup(); s.ApplicationBase = AppDomain.CurrentDomain.SetupInformation.Applicati onBase; AppDomain d = AppDomain.CreateDomain("TestDomain", AppDomain.CurrentDomain.Evidence, s);
d.DoCallBack(new CrossAppDomainDelegate(DomainCall)); // ... }
public static void DomainCall() { AppDomain.CurrentDomain.Load("MyAssembly"); } }
The main thing to make sure of is that your delegate does not
reference an instance method of a MarshalByRef object, or else the assembly will be loaded in the domain in which that object resides.
Hope that helps - Ken "Sam Martin" <sa*********@yahoo.co.uk> wrote in message news:eq*************@TK2MSFTNGP09.phx.gbl... > Hi All, > > I've got a problem where my application loads an assembly in the running > AppDomain when it shouldn't. > > Ok, I've got a RemotingHost application that configs the remoting stuff and > then... > asks the user for a list of .net DLLs. > the app then copies a these assemblies to a cache folder along with
my > RemotingClient app. Once copies i config a AppDomain setup and
create a new > AppDomain. > Once created, i loop through the user chosen assemblies and load
into the > AppDomain. I then AppDomain.ExecuteAssembly my RemotingClient. > > The purpose is so that I can dynamically load and unload assemblies and > report on type information to my main app (in this case the RemotingHost). > Everything works fine in principal, however when I load the DLLs
from my > cache folder the assembly is actually loaded in both AppDomains. > > I know if i reference a type across AppDomain, it will cause the
Framework > to load the assembly in the other AppDomain, but all i'm doing it is loading > it? > > Any ideas? (please help:) > > TIA > Sam Martin > > (code sample below) > > System.IO.Directory.CreateDirectory(Application.St artupPath+"\\cache"); > > // copy my RemotingClient.exe to the cache > > // Set up the AppDomainSetup > AppDomainSetup setup = new AppDomainSetup(); > setup.ApplicationBase = Application.StartupPath+"\\cache\\"; > setup.ConfigurationFile = ""; > > // Set up the Evidence > System.Security.Policy.Evidence baseEvidence = > AppDomain.CurrentDomain.Evidence; > System.Security.Policy.Evidence evidence = new > System.Security.Policy.Evidence(baseEvidence); > // evidence.AddAssembly("(some assembly)"); > > // Create the AppDomain > AppDomain newDomain = AppDomain.CreateDomain("temp", evidence, setup); > > foreach(string an in this.listBoxAsmList.Items) > { > > // copy the specified assembly to cache > > string asmn = an.ToLower().Replace(".dll",""); > > asmn = MyFuncToGetAsmDisplayName(an); > newDomain.Load(asmn); > } > > newDomain.ExecuteAssembly("RemotingClient.exe); > AppDomain.Unload(newDomain); > >
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Michael Culley |
last post by:
In vb6 it was possible to create an exe as an activeX exe and communicate
between 2 apps. Now we have remoting which requires opening a tcp port to
listen on, which seems kinda crappy cause another...
|
by: Mountain Bikn' Guy |
last post by:
I need some advice on this. I am working on a fairly complex calculator app
(C#) with lots of functions (and these functions in turn use math functions
from an unmanaged C DLL). A calculation takes...
|
by: Sharon |
last post by:
I’m trying to build a generic Publisher-Subscriber that will work over the
net, so I’m using the Remoting.
I wish that the subscriber user will be notify about the messages sent by
the...
|
by: Jody L. Whitlock |
last post by:
Okay, I've banged my head against a wall for over a year now. Maybe
I'm just a rock when it comes to this.
I've got a new project, a Windows Service. The "application" itself is
in a DLL that...
|
by: breeto |
last post by:
If you've configured .NET Remoting to use more than one channel of the
same type, for example two TcpClientChannels with unique names, when
you want to create a proxy to a remote object how do you...
|
by: mcoyote |
last post by:
So, the situation is that we have a poorly-executed UserControl that relies on a number of singletons in its assembly that unfortunately, over time, began acquiring the state of the control....
|
by: |
last post by:
If this is simple, forgive my ignorance, but I'm coming from the
CompactFramework where we don't use AppDomains. I did a fair bit of archive
searching and couldn't find an answer and I got no...
|
by: Dilip |
last post by:
I have a peculiar problem that I am not sure how to solve.
I have a C# application that has 2 appdomains. The default appdomain
just exposes a remoting end point that external applications can...
|
by: jeremyje |
last post by:
I would like to create an application where I have many concurrent
processes being managed by a monitoring process. Each process that is
"managed" will be invoked from an assembly dll (think...
|
by: CloudSolutions |
last post by:
Introduction:
For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
|
by: Faith0G |
last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome former...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
| |