How to add non dll dependencies in a ASP.Net project ?

[Michel de Becdelièvre]

Here is my scenario :

I have a library libA.dll, this library is built by a project
(projectA), which may be used by several "solutions"
=> 1 dll assembly
=> this library uses a xslt transform => there is a "A.xslt" file
that must be put somewhere inside the project that includes the library, and
a DTD, and a base xml file, and... all these files should be updated at the
same time as the dll

I know how I can tell Visual Studio that my main project depends on
projectA, I know that the library will be AUTOMATICALLY updated when I
change something and copied at the right place.

How can I tell Visual Studio.Net (2003) that I want A.xslt to be
AUTOMATICALLY updated in my main project when I change it in projectA ?

[Scott Allen]

One approach would be to add a build event to the class library
project (Project -> Properties -> Common Properties -> Build Events.
The build event can copy the file to the $(SolutionDir) destination.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Fri, 17 Jun 2005 11:22:00 +0200, "Michel de Becdelièvre"
<m_*****@msn.com> wrote:

Here is my scenario :

I have a library libA.dll, this library is built by a project
(projectA), which may be used by several "solutions"
=> 1 dll assembly
=> this library uses a xslt transform => there is a "A.xslt" file
that must be put somewhere inside the project that includes the library, and
a DTD, and a base xml file, and... all these files should be updated at the
same time as the dll

I know how I can tell Visual Studio that my main project depends on
projectA, I know that the library will be AUTOMATICALLY updated when I
change something and copied at the right place.

How can I tell Visual Studio.Net (2003) that I want A.xslt to be
AUTOMATICALLY updated in my main project when I change it in projectA ?

[Michel de Becdelièvre]

"Scott Allen" <sc***@nospam.odetocode.com> a écrit dans le message de news:
ih********************************@4ax.com...

One approach would be to add a build event to the class library
project (Project -> Properties -> Common Properties -> Build Events.
The build event can copy the file to the $(SolutionDir) destination.

--
Scott

I'll try that, but it's a "push" approach that does not take modification
times into account. I'd rather "pull" and use timestamps.

Strange there is no more answers : this should be a faily commn scenario if
you are writing Controls that need a Javascript library or a css style
sheet.

[Scott Allen]

The other option is to make the files embedded resources in the
assembly - that way the 'family always travels together' so to speak.
I think this is what you'll want if the XLST is being delivered at
runtime.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Fri, 17 Jun 2005 17:50:25 +0200, "Michel de Becdelièvre"
<m_*****@msn.com> wrote:

"Scott Allen" <sc***@nospam.odetocode.com> a écrit dans le message de news:
ih********************************@4ax.com...

One approach would be to add a build event to the class library
project (Project -> Properties -> Common Properties -> Build Events.
The build event can copy the file to the $(SolutionDir) destination.

--
Scott

I'll try that, but it's a "push" approach that does not take modification
times into account. I'd rather "pull" and use timestamps.

Strange there is no more answers : this should be a faily commn scenario if
you are writing Controls that need a Javascript library or a css style
sheet.

[Michel de Becdelièvre]

"Scott Allen" <sc***@nospam.odetocode.com> a écrit dans le message de news:
rh********************************@4ax.com...

The other option is to make the files embedded resources in the
assembly - that way the 'family always travels together' so to speak.
I think this is what you'll want if the XLST is being delivered at
runtime.

--

Great idea. I'll see if I can manage to implement this.

Do you know of a way to do this for JavaScript or css support files ? These
are not pulled out by C# code but by IIS directly.

[Scott Allen]

Well - for embedded script it will work best if you use
RegisterClientScriptBlock, like Phil here:
http://haacked.com/archive/2005/04/29/2879.aspx

Of course, you could change the IIS script mappings to route requests
for .js files through the ASP.NET runtime, and implement an
IHttpHandler to dig a script file it doesn't find on disk out of an
assembly...

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Fri, 17 Jun 2005 18:25:26 +0200, "Michel de Becdelièvre"
<m_*****@msn.com> wrote:

"Scott Allen" <sc***@nospam.odetocode.com> a écrit dans le message de news:
rh********************************@4ax.com...

The other option is to make the files embedded resources in the
assembly - that way the 'family always travels together' so to speak.
I think this is what you'll want if the XLST is being delivered at
runtime.

--

Great idea. I'll see if I can manage to implement this.

Do you know of a way to do this for JavaScript or css support files ? These
are not pulled out by C# code but by IIS directly.

[Michel de Becdelièvre]

"Scott Allen" <sc***@nospam.odetocode.com> a écrit dans le message de news:
th********************************@4ax.com...

Well - for embedded script it will work best if you use
RegisterClientScriptBlock, like Phil here:
http://haacked.com/archive/2005/04/29/2879.aspx

Of course, you could change the IIS script mappings to route requests
for .js files through the ASP.NET runtime, and implement an
IHttpHandler to dig a script file it doesn't find on disk out of an
assembly...

RegisterClientScriptBlock is *real bad news* for big scripts or scripts that
are reused at several places in the web site. Kills off all caching.