Binaries and installers

[CuriousGeorge]

I recently upgraded an ASP.Net 1.1 app to .Net 2.0 and am now struggling
with the different binary system used. Previously a binary was created in
the bin subfolder of my ASP.Net app. I could add that binary to my
installer. With ASP.Net 2.0 there are no binaries generated in the bin
subfolder. It appears they reside in a temporary location.

How do I reference these binaries for includion in my installer? Is there a
new step I need to perform to get the binaries in a known static location so
that my installer can easily find them?

-Brett-

[Jeffrey Tan[MSFT]]

Hi Brett,

Thanks for posting!

For the current issue, the compilation mode is different between the
ASP.NET v1.1 and the ASP.NET v2.0.

If you want to get the assembly of the current web application, you should
use the ¡°publish web site¡± function for the current issue. In the
¡°Solution Explorer¡± tab, please right click the node of the current
project. And then, choose the ¡°publish web site¡± option. You can publish
the current web application via the file system, IIS and FTP. For example,
if you publish the web application by using file system, you will get the
assembly file and aspx page file in the specific folder which you marked in
the dialog before.

Finally, add the assembly files and aspx pages file into the web setup
application. You will obtain the expected installer.

Hope this will be helpful. If you have any issues in the future, please
don¡¯t hesitate to let me know. It¡¯s my pleasure to be of assistant.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[CuriousGeorge]

Ah yes, I see that now. I had tried that previously but I was concerned
that the 'unique' file names were changing each time, turns out I was wrong
when you use the 'Use fixed naming and single page assemblies' option. This
allows me to include specific assembly names in my installer.

Thanks for the help!

-Brett-
""Jeffrey Tan[MSFT]"" <je***@online.microsoft.com> wrote in message
news:cO*************@TK2MSFTNGXA01.phx.gbl...

Hi Brett,

Thanks for posting!

For the current issue, the compilation mode is different between the
ASP.NET v1.1 and the ASP.NET v2.0.

If you want to get the assembly of the current web application, you should
use the ¡°publish web site¡± function for the current issue. In the
¡°Solution Explorer¡± tab, please right click the node of the current
project. And then, choose the ¡°publish web site¡± option. You can publish
the current web application via the file system, IIS and FTP. For example,
if you publish the web application by using file system, you will get the
assembly file and aspx page file in the specific folder which you marked
in
the dialog before.

Finally, add the assembly files and aspx pages file into the web setup
application. You will obtain the expected installer.

Hope this will be helpful. If you have any issues in the future, please
don¡¯t hesitate to let me know. It¡¯s my pleasure to be of assistant.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

[Jeffrey Tan[MSFT]]

Hi CuriousGeorge,

I am glad your problem is resolved. If you need further help, please feel
free to post. Thanks

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.