I have what I think should be a pretty common scenario in a corporate
environment. I have a web app and three environments on three servers:
Development, QA and Production.
We develop in development and then deploy the updated application to our QA
server and then once tested to our production server.
The application has a web.config file. The contents of the file
(appsettings part) are different in all three environments because each
enviroment connects to different databases (a dev, qa and the prod database).
what I'm discovering is that the Publish option in VS2005 won't work in this
scenario because it will copy web.config from development to QA or production
and thus result in the incorrect appsettings...i.e. Production all of a
sudden connecting to the development database.
Is there any way around this with the Publish command? Or do i have to
manually use "Copy Web" which is more timeconsuming?
Excluding web.config does't work because the web.config in the destination
is still wiped out. I tried setting web.config to Read ONly in QA and
production but it is still deleted and overwritten by the one from dev.
Seems like someone really didn't think of this common scenario. An "Exclude
web.config" checkbox would have been all that was necessary. Or is this
hidden somewhere?
Thx.
R- 8 1967
Not sure if this applies, but have your looked at using a user.config file?
(I assume this still works in 2.0?)
user.config
<appSettings>
<add key="ConnectionString"
value="server=(local);Trusted_Connection=true;data base=bar;Application
Name=foo" />
</appSettings>
web.config
<appSettings file="user.config">
<add key="ConnectionString"
value="server=PRODSERVER;Trusted_Connection=true;d atabase=bar;Application
Name=foo"/>
</appSettings>
My basic understanding is if the user.config is present it will use it,
otherwise it defaults to the values in web.config. Not sure if Publish,
copies user.config to server or not. Something to look into, hopefully
somebody else has a better solution for you.
Greg
"Robert" <ro*****@noemail.nospam> wrote in message
news:6C**********************************@microsof t.com... I have what I think should be a pretty common scenario in a corporate environment. I have a web app and three environments on three servers: Development, QA and Production.
We develop in development and then deploy the updated application to our QA server and then once tested to our production server.
The application has a web.config file. The contents of the file (appsettings part) are different in all three environments because each enviroment connects to different databases (a dev, qa and the prod database).
what I'm discovering is that the Publish option in VS2005 won't work in this scenario because it will copy web.config from development to QA or production and thus result in the incorrect appsettings...i.e. Production all of a sudden connecting to the development database.
Is there any way around this with the Publish command? Or do i have to manually use "Copy Web" which is more timeconsuming?
Excluding web.config does't work because the web.config in the destination is still wiped out. I tried setting web.config to Read ONly in QA and production but it is still deleted and overwritten by the one from dev.
Seems like someone really didn't think of this common scenario. An "Exclude web.config" checkbox would have been all that was necessary. Or is this hidden somewhere?
Thx. R-
re: An "Exclude web.config" checkbox would have been all that was necessary.
Doesn't selecting web.config in the Solution Explorer, and then going to the
menu "Website", and then clicking on "Exclude from project" work for you ?
What I would do, though, is include *all* connection strings in web.config and,
depending on the website's location, use the appropiate one.
Something like (pseudocode ) :
Dim dnsname As String = Request.Url.Host
If dnsname = domain1 Then
' request connection string 1 here
Elseif dnsname = domain2 Then
' request connection string 2 here
Else
' request connection string 3 here
End If
End If
That should take care of all your problems.
Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
Foros de ASP.NET en Español : http://asp.net.do/foros/
======================================
"Robert" <ro*****@noemail.nospam> wrote in message
news:6C**********************************@microsof t.com...I have what I think should be a pretty common scenario in a corporate environment. I have a web app and three environments on three servers: Development, QA and Production.
We develop in development and then deploy the updated application to our QA server and then once tested to our production server.
The application has a web.config file. The contents of the file (appsettings part) are different in all three environments because each enviroment connects to different databases (a dev, qa and the prod database).
what I'm discovering is that the Publish option in VS2005 won't work in this scenario because it will copy web.config from development to QA or production and thus result in the incorrect appsettings...i.e. Production all of a sudden connecting to the development database.
Is there any way around this with the Publish command? Or do i have to manually use "Copy Web" which is more timeconsuming?
Excluding web.config does't work because the web.config in the destination is still wiped out. I tried setting web.config to Read ONly in QA and production but it is still deleted and overwritten by the one from dev.
Seems like someone really didn't think of this common scenario. An "Exclude web.config" checkbox would have been all that was necessary. Or is this hidden somewhere?
Thx. R-
Thanks for your suggestion but it unfortunately is not an option in my case.
I tried using "exclude". When you use this, .net physically renames the
file in the dev site where i am developing to "web.config.exclude" which then
means that the dev site no longer works because there is no web.config.
Furthermore, when using the "publish" command, all of the files in the
destination are deleted first, irregardless of any "exclusion".
Even if I put all of the connection strings in the same web.config so it
could be identical in each environment i would still need to have a way to
know which environment i was actually running in and this would mean
hardcoding the url for example in a compiled file. Additionally in the
corporate environment where I am it is not permissible that I stored the
production credentials on the dev and qa sites although i do encrypt them.
And in some cases, i may not be allowed to know the production database
credentials which precludes them being the web.configs in each environments.
I think there really should have been a setting under options that just said
"exclude web.config" from publishing. And if checked, it 1) didn't delete a
web.config and 2) didn't copy or overwrite it either.
I am able to use the "copy web" to still deploy but it is significantly
slower than using publish and slower than the process under vs 2003.
Although theoretically if i just need to transfer a file or two, that is
faster.
thx.
r-
"Juan T. Llibre" wrote: re: An "Exclude web.config" checkbox would have been all that was necessary.
Doesn't selecting web.config in the Solution Explorer, and then going to the menu "Website", and then clicking on "Exclude from project" work for you ?
What I would do, though, is include *all* connection strings in web.config and, depending on the website's location, use the appropiate one.
Something like (pseudocode ) :
Dim dnsname As String = Request.Url.Host If dnsname = domain1 Then ' request connection string 1 here Elseif dnsname = domain2 Then ' request connection string 2 here Else ' request connection string 3 here End If End If
That should take care of all your problems.
Juan T. Llibre, ASP.NET MVP ASP.NET FAQ : http://asp.net.do/faq/ Foros de ASP.NET en Español : http://asp.net.do/foros/ ====================================== "Robert" <ro*****@noemail.nospam> wrote in message news:6C**********************************@microsof t.com...I have what I think should be a pretty common scenario in a corporate environment. I have a web app and three environments on three servers: Development, QA and Production.
We develop in development and then deploy the updated application to our QA server and then once tested to our production server.
The application has a web.config file. The contents of the file (appsettings part) are different in all three environments because each enviroment connects to different databases (a dev, qa and the prod database).
what I'm discovering is that the Publish option in VS2005 won't work in this scenario because it will copy web.config from development to QA or production and thus result in the incorrect appsettings...i.e. Production all of a sudden connecting to the development database.
Is there any way around this with the Publish command? Or do i have to manually use "Copy Web" which is more timeconsuming?
Excluding web.config does't work because the web.config in the destination is still wiped out. I tried setting web.config to Read ONly in QA and production but it is still deleted and overwritten by the one from dev.
Seems like someone really didn't think of this common scenario. An "Exclude web.config" checkbox would have been all that was necessary. Or is this hidden somewhere?
Thx. R-
re: Even if I put all of the connection strings in the same web.config so it could be identical in each environment i would still need to have a way to know which environment i was actually running in and this would mean hardcoding the url for example in a compiled file.
No, no, no !
The pseudocode I outlined would work in all 3 environments,
providing the correct connection string to all of them.
re: And in some cases, i may not be allowed to know the production database credentials which precludes them being the web.configs in each environments.
You should talk your web admins about the inadvisability of that.
If you are tasked with developing a production site,
it's only natural that you have access to the databases there.
Anything less than that only hobbles you...and not even they want that.
re: I am able to use the "copy web" to still deploy but it is significantly slower than using publish
I'll take that any day over not being able to do it at all.
;-)
Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
Foros de ASP.NET en Español : http://asp.net.do/foros/
======================================
"Robert" <ro*****@noemail.nospam> wrote in message
news:AC**********************************@microsof t.com... Thanks for your suggestion but it unfortunately is not an option in my case.
I tried using "exclude". When you use this, .net physically renames the file in the dev site where i am developing to "web.config.exclude" which then means that the dev site no longer works because there is no web.config. Furthermore, when using the "publish" command, all of the files in the destination are deleted first, irregardless of any "exclusion".
Even if I put all of the connection strings in the same web.config so it could be identical in each environment i would still need to have a way to know which environment i was actually running in and this would mean hardcoding the url for example in a compiled file. Additionally in the corporate environment where I am it is not permissible that I stored the production credentials on the dev and qa sites although i do encrypt them. And in some cases, i may not be allowed to know the production database credentials which precludes them being the web.configs in each environments.
I think there really should have been a setting under options that just said "exclude web.config" from publishing. And if checked, it 1) didn't delete a web.config and 2) didn't copy or overwrite it either.
I am able to use the "copy web" to still deploy but it is significantly slower than using publish and slower than the process under vs 2003. Although theoretically if i just need to transfer a file or two, that is faster.
thx. r-
"Juan T. Llibre" wrote:
re: > An "Exclude web.config" checkbox would have been all that was necessary.
Doesn't selecting web.config in the Solution Explorer, and then going to the menu "Website", and then clicking on "Exclude from project" work for you ?
What I would do, though, is include *all* connection strings in web.config and, depending on the website's location, use the appropiate one.
Something like (pseudocode ) :
Dim dnsname As String = Request.Url.Host If dnsname = domain1 Then ' request connection string 1 here Elseif dnsname = domain2 Then ' request connection string 2 here Else ' request connection string 3 here End If End If
That should take care of all your problems.
Juan T. Llibre, ASP.NET MVP ASP.NET FAQ : http://asp.net.do/faq/ Foros de ASP.NET en Español : http://asp.net.do/foros/ ====================================== "Robert" <ro*****@noemail.nospam> wrote in message news:6C**********************************@microsof t.com... >I have what I think should be a pretty common scenario in a corporate > environment. I have a web app and three environments on three servers: > Development, QA and Production. > > We develop in development and then deploy the updated application to our QA > server and then once tested to our production server. > > The application has a web.config file. The contents of the file > (appsettings part) are different in all three environments because each > enviroment connects to different databases (a dev, qa and the prod database). > > what I'm discovering is that the Publish option in VS2005 won't work in this > scenario because it will copy web.config from development to QA or production > and thus result in the incorrect appsettings...i.e. Production all of a > sudden connecting to the development database. > > Is there any way around this with the Publish command? Or do i have to > manually use "Copy Web" which is more timeconsuming? > > Excluding web.config does't work because the web.config in the destination > is still wiped out. I tried setting web.config to Read ONly in QA and > production but it is still deleted and overwritten by the one from dev. > > Seems like someone really didn't think of this common scenario. An "Exclude > web.config" checkbox would have been all that was necessary. Or is this > hidden somewhere? > > Thx. > R-
Obviously I'll have to stick with Copy Web. I work for a financial
institution (bank) and there are very strict government regulations so
security is currently a very, very big concern.
Thanks for your suggestions!
"Juan T. Llibre" wrote: re: Even if I put all of the connection strings in the same web.config so it could be identical in each environment i would still need to have a way to know which environment i was actually running in and this would mean hardcoding the url for example in a compiled file.
No, no, no !
The pseudocode I outlined would work in all 3 environments, providing the correct connection string to all of them.
re: And in some cases, i may not be allowed to know the production database credentials which precludes them being the web.configs in each environments.
You should talk your web admins about the inadvisability of that.
If you are tasked with developing a production site, it's only natural that you have access to the databases there.
Anything less than that only hobbles you...and not even they want that.
re: I am able to use the "copy web" to still deploy but it is significantly slower than using publish
I'll take that any day over not being able to do it at all.
;-)
Juan T. Llibre, ASP.NET MVP ASP.NET FAQ : http://asp.net.do/faq/ Foros de ASP.NET en Español : http://asp.net.do/foros/ ====================================== "Robert" <ro*****@noemail.nospam> wrote in message news:AC**********************************@microsof t.com... Thanks for your suggestion but it unfortunately is not an option in my case.
I tried using "exclude". When you use this, .net physically renames the file in the dev site where i am developing to "web.config.exclude" which then means that the dev site no longer works because there is no web.config. Furthermore, when using the "publish" command, all of the files in the destination are deleted first, irregardless of any "exclusion".
Even if I put all of the connection strings in the same web.config so it could be identical in each environment i would still need to have a way to know which environment i was actually running in and this would mean hardcoding the url for example in a compiled file. Additionally in the corporate environment where I am it is not permissible that I stored the production credentials on the dev and qa sites although i do encrypt them. And in some cases, i may not be allowed to know the production database credentials which precludes them being the web.configs in each environments.
I think there really should have been a setting under options that just said "exclude web.config" from publishing. And if checked, it 1) didn't delete a web.config and 2) didn't copy or overwrite it either.
I am able to use the "copy web" to still deploy but it is significantly slower than using publish and slower than the process under vs 2003. Although theoretically if i just need to transfer a file or two, that is faster.
thx. r-
"Juan T. Llibre" wrote:
re: > An "Exclude web.config" checkbox would have been all that was necessary.
Doesn't selecting web.config in the Solution Explorer, and then going to the menu "Website", and then clicking on "Exclude from project" work for you ?
What I would do, though, is include *all* connection strings in web.config and, depending on the website's location, use the appropiate one.
Something like (pseudocode ) :
Dim dnsname As String = Request.Url.Host If dnsname = domain1 Then ' request connection string 1 here Elseif dnsname = domain2 Then ' request connection string 2 here Else ' request connection string 3 here End If End If
That should take care of all your problems.
Juan T. Llibre, ASP.NET MVP ASP.NET FAQ : http://asp.net.do/faq/ Foros de ASP.NET en Español : http://asp.net.do/foros/ ====================================== "Robert" <ro*****@noemail.nospam> wrote in message news:6C**********************************@microsof t.com... >I have what I think should be a pretty common scenario in a corporate > environment. I have a web app and three environments on three servers: > Development, QA and Production. > > We develop in development and then deploy the updated application to our QA > server and then once tested to our production server. > > The application has a web.config file. The contents of the file > (appsettings part) are different in all three environments because each > enviroment connects to different databases (a dev, qa and the prod database). > > what I'm discovering is that the Publish option in VS2005 won't work in this > scenario because it will copy web.config from development to QA or production > and thus result in the incorrect appsettings...i.e. Production all of a > sudden connecting to the development database. > > Is there any way around this with the Publish command? Or do i have to > manually use "Copy Web" which is more timeconsuming? > > Excluding web.config does't work because the web.config in the destination > is still wiped out. I tried setting web.config to Read ONly in QA and > production but it is still deleted and overwritten by the one from dev. > > Seems like someone really didn't think of this common scenario. An "Exclude > web.config" checkbox would have been all that was necessary. Or is this > hidden somewhere? > > Thx. > R- http://dvxp.com/discus/messages/1/149.html?1071180598
This is interesting. The recommendation here is to put the user.config file
on the production server and not on the development server. That way you
don't have to worry about it being copied at all.
Does Publish really purge the destination folder first? I can't get it to
do that will my quick test.
Greg
"Greg Burns" <bl*******@newsgroups.nospam> wrote in message
news:ub**************@TK2MSFTNGP12.phx.gbl... Not sure if this applies, but have your looked at using a user.config file? (I assume this still works in 2.0?)
user.config <appSettings> <add key="ConnectionString" value="server=(local);Trusted_Connection=true;data base=bar;Application Name=foo" /> </appSettings>
web.config <appSettings file="user.config"> <add key="ConnectionString" value="server=PRODSERVER;Trusted_Connection=true;d atabase=bar;Application Name=foo"/> </appSettings>
My basic understanding is if the user.config is present it will use it, otherwise it defaults to the values in web.config. Not sure if Publish, copies user.config to server or not. Something to look into, hopefully somebody else has a better solution for you.
Greg "Robert" <ro*****@noemail.nospam> wrote in message news:6C**********************************@microsof t.com...I have what I think should be a pretty common scenario in a corporate environment. I have a web app and three environments on three servers: Development, QA and Production.
We develop in development and then deploy the updated application to our QA server and then once tested to our production server.
The application has a web.config file. The contents of the file (appsettings part) are different in all three environments because each enviroment connects to different databases (a dev, qa and the prod database).
what I'm discovering is that the Publish option in VS2005 won't work in this scenario because it will copy web.config from development to QA or production and thus result in the incorrect appsettings...i.e. Production all of a sudden connecting to the development database.
Is there any way around this with the Publish command? Or do i have to manually use "Copy Web" which is more timeconsuming?
Excluding web.config does't work because the web.config in the destination is still wiped out. I tried setting web.config to Read ONly in QA and production but it is still deleted and overwritten by the one from dev.
Seems like someone really didn't think of this common scenario. An "Exclude web.config" checkbox would have been all that was necessary. Or is this hidden somewhere?
Thx. R-
I guess my test was a little too quick. I see that it DOES purge first.
bummer
"Greg Burns" <bl*******@newsgroups.nospam> wrote in message
news:uN**************@TK2MSFTNGP10.phx.gbl... http://dvxp.com/discus/messages/1/149.html?1071180598
This is interesting. The recommendation here is to put the user.config file on the production server and not on the development server. That way you don't have to worry about it being copied at all.
Does Publish really purge the destination folder first? I can't get it to do that will my quick test.
Greg
"Greg Burns" <bl*******@newsgroups.nospam> wrote in message news:ub**************@TK2MSFTNGP12.phx.gbl... Not sure if this applies, but have your looked at using a user.config file? (I assume this still works in 2.0?)
user.config <appSettings> <add key="ConnectionString" value="server=(local);Trusted_Connection=true;data base=bar;Application Name=foo" /> </appSettings>
web.config <appSettings file="user.config"> <add key="ConnectionString" value="server=PRODSERVER;Trusted_Connection=true;d atabase=bar;Application Name=foo"/> </appSettings>
My basic understanding is if the user.config is present it will use it, otherwise it defaults to the values in web.config. Not sure if Publish, copies user.config to server or not. Something to look into, hopefully somebody else has a better solution for you.
Greg "Robert" <ro*****@noemail.nospam> wrote in message news:6C**********************************@microsof t.com...I have what I think should be a pretty common scenario in a corporate environment. I have a web app and three environments on three servers: Development, QA and Production.
We develop in development and then deploy the updated application to our QA server and then once tested to our production server.
The application has a web.config file. The contents of the file (appsettings part) are different in all three environments because each enviroment connects to different databases (a dev, qa and the prod database).
what I'm discovering is that the Publish option in VS2005 won't work in this scenario because it will copy web.config from development to QA or production and thus result in the incorrect appsettings...i.e. Production all of a sudden connecting to the development database.
Is there any way around this with the Publish command? Or do i have to manually use "Copy Web" which is more timeconsuming?
Excluding web.config does't work because the web.config in the destination is still wiped out. I tried setting web.config to Read ONly in QA and production but it is still deleted and overwritten by the one from dev.
Seems like someone really didn't think of this common scenario. An "Exclude web.config" checkbox would have been all that was necessary. Or is this hidden somewhere?
Thx. R-
re: Does Publish really purge the destination folder first?
It does...
Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
Foros de ASP.NET en Español : http://asp.net.do/foros/
======================================
"Greg Burns" <bl*******@newsgroups.nospam> wrote in message
news:uN**************@TK2MSFTNGP10.phx.gbl... http://dvxp.com/discus/messages/1/149.html?1071180598
This is interesting. The recommendation here is to put the user.config file on the production server and not on the development server. That way you don't have to worry about it being copied at all.
Does Publish really purge the destination folder first? I can't get it to do that will my quick test.
Greg
"Greg Burns" <bl*******@newsgroups.nospam> wrote in message news:ub**************@TK2MSFTNGP12.phx.gbl... Not sure if this applies, but have your looked at using a user.config file? (I assume this still works in 2.0?)
user.config <appSettings> <add key="ConnectionString" value="server=(local);Trusted_Connection=true;data base=bar;Application Name=foo" /> </appSettings>
web.config <appSettings file="user.config"> <add key="ConnectionString" value="server=PRODSERVER;Trusted_Connection=true;d atabase=bar;Application Name=foo"/> </appSettings>
My basic understanding is if the user.config is present it will use it, otherwise it defaults to the values in web.config. Not sure if Publish, copies user.config to server or not. Something to look into, hopefully somebody else has a better solution for you.
Greg "Robert" <ro*****@noemail.nospam> wrote in message news:6C**********************************@microsof t.com...I have what I think should be a pretty common scenario in a corporate environment. I have a web app and three environments on three servers: Development, QA and Production.
We develop in development and then deploy the updated application to our QA server and then once tested to our production server.
The application has a web.config file. The contents of the file (appsettings part) are different in all three environments because each enviroment connects to different databases (a dev, qa and the prod database).
what I'm discovering is that the Publish option in VS2005 won't work in this scenario because it will copy web.config from development to QA or production and thus result in the incorrect appsettings...i.e. Production all of a sudden connecting to the development database.
Is there any way around this with the Publish command? Or do i have to manually use "Copy Web" which is more timeconsuming?
Excluding web.config does't work because the web.config in the destination is still wiped out. I tried setting web.config to Read ONly in QA and production but it is still deleted and overwritten by the one from dev.
Seems like someone really didn't think of this common scenario. An "Exclude web.config" checkbox would have been all that was necessary. Or is this hidden somewhere?
Thx. R-
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Darwin Fisk |
last post by:
I have an app that is deployed that uses .config file settings. I have an
update of that app that I am installing using a setup and deployment
project. The basic setup process works fine. Now I...
|
by: Marek |
last post by:
Hi there,
my WinForm application has to be installed in "no-touch-deployment" mode, so
users can run it from the web. I need to read application's .config file but
it does not work in ...
|
by: bene |
last post by:
i have an application written in vc 7.0
deploying it to XP or win2k is not problem
however, for win98 and winme, the oleacc.dll that comes with the
installation packet(.msi, instmsi?.exe)...
|
by: Juggler |
last post by:
Hi all
I've written a program in VB.NET that allows the user to build quotes for installing shower enclosures. As part of the program, I've included a blank Access database. I've provided them...
|
by: Joel H |
last post by:
We have several settings in web.config that are different on the developer
side than the production side. Our website sourcecode is under sourcesafe
control, so before we code, we check out the...
|
by: =?Utf-8?B?RHVrZSAoQU4yNDcp?= |
last post by:
I've added a web deployment project and want to use the config section
replacement but I'm obviously not understanding something.
I have set up an alternate appSettings file,...
|
by: shapper |
last post by:
Hello,
I am using VS 2008 and and just downloaded Web Deployment Projects:
http://connect.live.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=319288
I need the connection string in my...
|
by: DGleeson3 |
last post by:
Hello All
Hope Im posting in the right place. If not please point me elsewhere.
We are developing a reasonably standard Web application. VS2005
ASP.NET SQL server 2005.
The unusual...
|
by: tshad |
last post by:
I have a Windows Service that I am deploying by setting a Deployment project
in my solution.
The problem I am having is with the app.config file. This where we store
our connection string and...
|
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: Charles Arthur |
last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
|
by: aa123db |
last post by:
Variable and constants
Use var or let for variables and const fror constants.
Var foo ='bar';
Let foo ='bar';const baz ='bar';
Functions
function $name$ ($parameters$) {
}
...
|
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: 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...
| |